I’m running Scrivener 3.3.2 on Macbook Air (2020 model) using Big Sur 11.7.8
It has been stable with no issues for the past year or so, but crashed overnight and when I tried to re-open this morning, I got a very long error report. As a new poster here, I can’t embed the image but a copy-and-paste of the first part is below. I’m assuming this might be related to the auto-update for 3.3.2. I’ve tried closing everything and restarting with no success, and that is about the limits of my tech skills.
Can anyone tell me from this what the source of the problem might be? Is there a simple fix, like updating my OS or un-installing/reinstalling Scrivener?
I rely on Scrivener for work so this is a BIG issue.
Error report copy/paste:
Process: Scrivener [1213]
Path: /Applications/Scrivener.app/Contents/MacOS/Scrivener
Identifier: com.literatureandlatte.scrivener3
Version: 3.3.2 (15830)
App Item ID: 1310686187
App External ID: 860192370
Code Type: ARM-64 (Native)
Parent Process: ??? [1]
Responsible: Scrivener [1213]
User ID: 501
Date/Time: 2023-09-27 11:35:06.504 +1300
OS Version: macOS 11.7.8 (20G1351)
Report Version: 12
Anonymous UUID: 5CD0D5DB-E22A-A479-0487-577EF41B8E88
Time Awake Since Boot: 3200 seconds
System Integrity Protection: enabled
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY
Termination Signal: Segmentation fault: 11
Termination Reason: Namespace SIGNAL, Code 0xb
Terminating Process: exc handler [1213]
VM Regions Near 0:
→
__TEXT 10284c000-103df0000 [ 21.6M] r-x/r-x SM=COW /Applications/Scrivener.app/Contents/MacOS/Scrivener
Application Specific Information:
dyld: launch, running initializers
/Applications/Scrivener.app/Contents/MacOS/Scrivener
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread