Crash log attached and short version below
I had OBS last open 3 weeks ago and started adding new audio & camera devices. Then I went to open the next day and it crashed and hasn't opened since...wiping and reinstalling hasn't helped, clearing space on my MAC hasn't helped. Any thoughts?
Process: obs [39331]
Path: /Applications/OBS.app/Contents/MacOS/obs
Identifier: com.obsproject.obs-studio
Version: 25.0.7 (25.0.7)
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: obs [39331]
User ID: 501
Date/Time: 2020-04-20 16:26:05.455 +0100
OS Version: Mac OS X 10.13.6 (17G12034)
Report Version: 12
Anonymous UUID: 1E03BD2A-922B-540E-06B4-A88A8DDDFE64
Sleep/Wake UUID: 4EF6DE9A-90F4-4EB2-88CE-6B91E7F1A034
Time Awake Since Boot: 100000 seconds
Time Since Wake: 1200 seconds
System Integrity Protection: enabled
Crashed Thread: 13
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000020
Exception Note: EXC_CORPSE_NOTIFY
Termination Signal: Segmentation fault: 11
Termination Reason: Namespace SIGNAL, Code 0xb
Terminating Process: exc handler [0]
VM Regions Near 0x20:
-->
Kernel Alloc Once 000000000fd37000-000000000fd39000 [ 8K] rw-/rwx SM=PRV
I had OBS last open 3 weeks ago and started adding new audio & camera devices. Then I went to open the next day and it crashed and hasn't opened since...wiping and reinstalling hasn't helped, clearing space on my MAC hasn't helped. Any thoughts?
Process: obs [39331]
Path: /Applications/OBS.app/Contents/MacOS/obs
Identifier: com.obsproject.obs-studio
Version: 25.0.7 (25.0.7)
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: obs [39331]
User ID: 501
Date/Time: 2020-04-20 16:26:05.455 +0100
OS Version: Mac OS X 10.13.6 (17G12034)
Report Version: 12
Anonymous UUID: 1E03BD2A-922B-540E-06B4-A88A8DDDFE64
Sleep/Wake UUID: 4EF6DE9A-90F4-4EB2-88CE-6B91E7F1A034
Time Awake Since Boot: 100000 seconds
Time Since Wake: 1200 seconds
System Integrity Protection: enabled
Crashed Thread: 13
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000020
Exception Note: EXC_CORPSE_NOTIFY
Termination Signal: Segmentation fault: 11
Termination Reason: Namespace SIGNAL, Code 0xb
Terminating Process: exc handler [0]
VM Regions Near 0x20:
-->
Kernel Alloc Once 000000000fd37000-000000000fd39000 [ 8K] rw-/rwx SM=PRV
Attachments
-
Screen Shot 2020-04-20 at 7.51.03 pm.png508.7 KB · Views: 59
-
Screen Shot 2020-04-20 at 7.51.06 pm.png720.3 KB · Views: 55
-
Screen Shot 2020-04-20 at 7.51.09 pm.png595.9 KB · Views: 70
-
Screen Shot 2020-04-20 at 7.51.12 pm.png618.4 KB · Views: 111
-
Screen Shot 2020-04-20 at 7.51.15 pm.png674.5 KB · Views: 112
-
Screen Shot 2020-04-20 at 7.51.20 pm.png868.8 KB · Views: 32
-
Screen Shot 2020-04-20 at 7.51.25 pm.png990.1 KB · Views: 35
-
Screen Shot 2020-04-20 at 7.51.29 pm.png921.3 KB · Views: 45
-
Screen Shot 2020-04-20 at 7.51.32 pm.png906 KB · Views: 80
-
Screen Shot 2020-04-20 at 7.51.42 pm.png646.5 KB · Views: 39