Hello, I don’t have enough to file an actual bug report, but this started happening directly after the update to 26.5.1 yesterday on a MacBook Air M4. I have been editing in two related projects, before and now after, updating to 26.5.1. After the update text editing can be slow, as in 4 or 5 letters behind what I am typing. I know updates can entail a lot of background processing, but I only notice the slowdown in Scrivener. My reason for posting this topic is that Scrivener has been randomly crashing for two days now. I have rebooted. The crash happens randomly (I cannot see a specific cause) when I have made a correction in the text. Luckily, I have only lost the correction that I was doing just before the crash. It doesn’t crash every time, just randomly.
Update: I decided to put my laptop into ‘safe mode’ because it does a quick disk repair before it fully boots up, and certain system caches get cleared and rebuilt, so it was worth a try. After it came up in safe mode, I rebooted it. It seems so far to have fixed crash problems in other apps, and I am working in Scrivener without any problems so far.
Thanks for the update! It’s never a bad idea to use safe mode after a system update, if some programs are repeatedly crashing. Not only does it flush caches and such, as you mention, but it also gives you a chance to try the software on its own, without any other background utilities running. With how intermeshed software is on a Mac, a clipboard utility that is in need of an update to fix a bug caused by the OS upgrade can cause instability in other software too.
I have the same symptoms - repeated crashes after update to macOS 26.5.1. Still happening after restarting in safe mode. Any ideas for next steps?
Should someone report this to Apple? Do they need to fix the bug? or is it a Scrivener problem? Just wondering, because I haven’t updated my mac mini yet and I don’t want to have the same problem.
So much for the ‘safe mode’ cleanup. Scrivener just crashed again. This time I had a project open, but was doing nothing with it. I was working in another app: Notes. I decided not to take a chance writing in Scrivener, so I used Notes with the intention to cut-and-paste when I was done. I needed some text from the Scrivener project, so I switched to the project, copied and pasted into notes, and a little bit later, I realized that the text that I had copied needed the word “be” in it, so I went back to the project, typed “be”, went back to Notes and a bit later I got the popup that Scrivener had crashed while I was in Notes. I am going to try to go back to the prior macOS release, and wait out the process of who takes responsibility to fix this.
For what it’s worth, I’ve been heavily using Scrivener 3.5.2 on macOS 26.5.1 on a macBook Air M4 that has a lot of memory and disk available, since the macOS update was released and I absently-minded upgraded. Seeing no issue here. No doubt the crashes caused by some unique issue buried somewhere in some software. Dunno.
I tried something else. I went into Settings - General - Login Items & Extensions and turned everything off, except DropboxUpdater. I figured that the way Scrivener would crash a short while after I had edited something in a text, or added to it, that it might be Dropbox that was causing the problem. Either Scrivener updating dropbox, or dropbox noticing that there were updates and sending out the updates to their cloud, seems to be the site of the crash. After turning all the login stuff off, except dropbox, and then opened my project and worked, and after a spell, Scrivener would crash. I turned off the DropboxUpdater, and turned on every other login item, and worked for over an hour without any crash. So it seems to be the updater. The thing is, everything that I was doing was still going into Dropbox — I could see the Dropbox icon at the top of my display showing that it was doing it. So I’m wondering what the DropboxUpdater is actually for. I am leaving it turned off for now.
I’m having a similar issue. Scrivener’s crashed 5 times in a week. Today it crashed while I was changing appearance settings. I’m using an M1 MacBook Pro. This is a relatively new issue.
Me too. It’s very weird. Today’s crash happened while changing while in Appearance settings.
I’m having the same experience. As of today, 6•13•26, Scrivener 3.5.2 has crashed. It happened today while I was in Scrivener’s Settings/Appearance/General Interface. I unchecked Monochrome Toolbars and it crashed. I was able to reproduce it twice. Then it stopped. Weird.
I would imagine it has to do with keeping Dropbox up to date, but you’d have to ask them about it. The fact that such an unrelated setting would have an impact on other software is peculiar, for sure.
Thanks for providing some information on what you were doing. So to confirm, when you say you are seeing a similar thing, you also have Dropbox installed, and were able to control the rate of crashing by adjusting its extensions? Was the appearance toggle with or without DropboxUpdater enabled?
No. I no longer use Dropbox. I sync Scrivener files between my Macs and have had no problems. In fact, I suspect my project may be corrupted so I’m going to deal with that and see what happens.