Both times, the app crashed without warning… the second was just when I created a new project and selected a folder to save to… it just froze. Does Scrivener work on a Mac?
I was working on it on MacBook Air today. No issues. Ran the update on my M1 Mini too, and that worked fine.
What version of Scrivener?
What does the crash report say?
Have you successfully run Scrivener on this machine before?
Hi @kewms, As I said, I hadn’t managed to type in anything - it was a fresh install of the latest from the Scrivener website yesterday (it’s reporting 3.3.1). There was no crash report - it just froze. I have not run Scrivener on this machine before. I think before I even got to that stage it bombed out & I had to restart.
Is there a specific reason to stay on 12.3? I’d update to 12.6.4 (which is just a few days old) 12.6.5 now. Still Monterey, but including all Monterey bug fixes. Maybe it helps.
1 Like
For indeterminate crashing (which to be clear is very unusual on the Mac outside of one known issue involving a crash when closing the software, that some experience with regularity), these general troubleshooting tips should be followed.
Unusual? Maybe… but this was within a few minutes of installing the app 
The crash report summary is:
-------------------------------------
Translated Report (Full Report Below)
-------------------------------------
Process: Scrivener [28566]
Path: /Applications/Scrivener.app/Contents/MacOS/Scrivener
Identifier: com.literatureandlatte.scrivener3
Version: 3.3.1 (15588)
Code Type: ARM-64 (Native)
Parent Process: launchd [1]
User ID: 501
Date/Time: 2023-04-09 17:19:13.1854 -0400
OS Version: macOS 12.3 (21E230)
Report Version: 12
Anonymous UUID: FC071535-1907-49AF-B960-7966805CD092
Sleep/Wake UUID: 76E1F84B-D3C2-4D63-AD3E-6EFD7834B186
Time Awake Since Boot: 4200000 seconds
Time Since Wake: 753 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 0x0000000000000010
Exception Codes: 0x0000000000000001, 0x0000000000000010
Exception Note: EXC_CORPSE_NOTIFY
Termination Reason: Namespace SIGNAL, Code 11 Segmentation fault: 11
Terminating Process: exc handler [28566]
Just upgraded to 13.3.1. I was really looking forward to using Scrivener!!
To clarify, one can have a tool that causes Scrivener to crash, which will within seconds cause it to crash the moment you install it and try to run it. The suggestions I provided are to help provide further clarity in whether that is an issue (and again, it is the most common reason for crashing, followed closely by content-specific problems, like corrupted graphics in the text editor, but you mentioned it happens in new projects, so we can rule that out).