I need my writing machine to be 100% reliable, so I downgraded to Ventura for the time being… I had to create a bootable USB installer, erase the hard drive, and then restore again from an earlier backup. I guess I’ll wait a while longer before upgrading to Sonoma…
I downgraded to Ventura 13.6 / Scrivener 3.3.2, back to 100% stable. I’ll wait for Sonoma 14.1 before trying that OS upgrade again.
1 Like
To update: we have received data that should help us trace down the crash. I was able to reproduce a few different crashes from it, but hopefully they stem from the same underlying cause.
This project also demonstrated the text overlapping bug some have been seeing. Whether that is related to the crashing remains to be seen.
3 Likes
Following. I’m having the same or very similar issue. Possible wrinkle is that even though Scrivener disappears and is reported as crashed (with offer to send results to Apple), it is still open when looking at Force Quit. And is still “Open” after forcing it to quit and trying to reload the program.
Please try this build and let me know if it helps:
[Link removed]
Many thanks,
Keith
Just chipping in since I’m not seeing any other replies. No change for me on MacOS, but I’m a novice with new builds and not sure that I am using the files correctly.
The 3.3.3 update crashed for me as well on Sonoma. The cursor appeared in strange positions (offset ro the right from the actual position) and words were autocompleted with nonsense when typing. This is in scriptwriting mode using an existing document with a modified template (based on a UK Stage Play).
The new test build resolves the crashes and autocompletion errors for me. The cursor still behaves weirdly when using the arrow keys to navigate. Sometimes I can’t use the left arrow key and have to use the mouse to reposition the cursor, which seems to reset it. This is in an existing scriptwriting project however, I have yet to reproduce it in a new document using a stock template. So it’s probably due to the modified template I’m using.
We’re narrowed down on it being bug that entirely requires Page View and some degree of text zoom being applied to the text. Anyone that can live without either of those together, should be able to avoid problems. That might explain why a new project doesn’t exhibit any issues, for unless you change your preferences to apply Page View and zoom to all new projects, all new projects will have neither of those conditions.
I think that checks out, my text zoom was set at 125%. Didn’t even notice that before. Though “Page View” isn’t enabled. Setting zoom to 100% seems to resolve the issue with the cursor.
Unfortunately Scrivener still crashes when writing (quite consistently after writing a few words). I’ve attached a log.
This is with:
- Text zoom at 100%
- Script Mode enabled
- Page view disabled
Scrivener Log.txt.zip (11.5 KB)
Just to make sure we’re on the same page, this is the latest test build, which for us internally has the best avoidance for crashing. All of the previous test builds you may encounter links to are quite easy to crash.
There is still one outstanding crash I’ve reproduced with that build (to be clear, the first one, not the “OldCaret” build), but otherwise I’ve not been able to crash it with normal text editing, even with a zoomed page view.
Sorry this is all a mess, but there are three slightly different reports, and we don’t know how connected they are, otherwise we’d consolidate the threads.
To be clear, although for the time being I have reverted to MacOS Ventura, when I was running Sonoma + 3.3.3, I was using 150% zoom but definitely not using Page View. I didn’t see any other strange behavior, just a reoccurring crash when I was editing / typing new text into a document. No problems (with that same binder) since I’ve reverted.
Just upgraded to Sonoma last night. Working on a Macbook Pro 2018 15". Started off ok for first ten minutes, then persistent crashes.
I have similar problems. 3.3.3 crashes on Sonoma 14.0 (23A344) if I type anything. When I reopen the document, Scrivener rebuilds the indexes. If I can type anything before the crash, there is a 50/50 chance it will be saved. I sent the crash file to L&L.
Hi i’m having the same issue. I tried to copy my project to new project which seem to help temporarily. The issue has now returned and constantly crashing which is very frustrating whilst your in the middle of writing. Is there any updates or a is there a bug fix being released ?
If you look on the forum, there are other threads where KB has posted beta versions try to pinpoint the causes of problems. Check them
2 Likes
I have the same issue. 3.3.3 crashes on Sonoma 14.0 if I type anything, usually 2nd or 3rd letter if I’m lucky. When I reopen, Scrivener rebuilds the indexes. The same issue happens again. I resaved project with new title and still happening. Any solutions out there?
Are you using “Script Mode”?
Turning off “Correct spelling errors as you type” in Scrivener > Settings > Corrections stopped Scrivener from crashing for me. Another option would be to disable “Suggest completions as you type” as a workaround.
1 Like
Please consolidate all conversation over in this thread, which ended up getting more traffic and testing discussion. And please make sure to scan the thread for updates from staff (with the shield icon beside the profile name). There are test builds available, such as the one I linked to here, and in the post directly above.
1 Like