Has anyone encountered Crashing of Scrivener on Mac OS 26.4 ?
I am having the issue on a Mac Studio M1 & the MacBook Neo. They both had MacOS 26.4 and I have a funny feeling Apple changed something in the code base and how it works.
Is there another thread about this or am I the only one encountering this issue.
I just can’t get anything done.
Thanks guys
I’ve been using it daily on my M1 MBP, not encountered any new issues (except a weird blurred screen thing)
I have been using iOS and it works fine.
With Mac OSX 26.4 when you click the master top level file name for your project the software quits. I have replicated this on the Mac Studio & Mac Neo.
The bug is there. Where did it come from ? Software changes by Apple. But it is there.
Hope this gets fixed.
Thanks
Does not happen with MacBook m1 running Mac OSX 26.3.1
I was thinking about installing Tahoe in the next week or so. I guess not, huh?
I’ve been using Tahoe in extremely intensive development work with dozens of apps at once since release and honestly have encountered very few issues.
I mean… I don’t like it. But it works and is stable (for me ymmv etc etc)
Yeah, but “crashes Scrivener” earns it a hard no from me.
I’ve just upgraded to 26.4 on M2Pro Mac Mini and have been using Scrivener for hours at a time since, and no sign of a crash so far (I also have 26.4 installed on my M1 MBA, but haven’t been using it much).
The rounded corners on everything are ridiculous, but I can ignore them; all the other software I use has been working without problem. The only exception is SoundSource by Rogue Amoeba, which isn’t working on the MBA, but is on the Mac Mini.
Just my experience.
Mark
I seriously doubt this was because of Tahoe.
With Mac OSX 26.4 when you click the master top level file name for your project the software quits. I have replicated this on the Mac Studio & Mac Neo.
I can’t replicate this with MacOS 26.4 on either a Mac Studio M2 or an MBA M4 – Scrivener has worked fine on both of them (including clicking on the tope level name) since I installed it on the day of release.
(Forgive me if you know what follows, but you don’t mention any crash messages, so in case you haven’t already done so, here are the normal steps you’d take to help the developers work out what’s going on.)
When a program crashes, a crash log is usually produced. To find them, open the Console app (in Applications > Utilities > Console in Finder) and then open the Crash Reports folder in the left hand panel. If Scrivener has crashed, there should be a log there named after the faulty program.
Click on the one for Scrivener, and then use the Share button to attach it to an email to scrivener-mac@literatureandlatte.com, with as much detail as you have about the circumstances of the crash.
Again, sorry if you knew all this!
I am also running MacOS 26.4 with daily scrivener use on a M3 MacBook Air and a M4 Mac mini, and have yet to experience a crash.
Same here on a MacBook Pro M1 Pro and a MacBook Air M3 — no crashes at all under 26.4.
M1 Mini, 26.4, no Scrivener crashes.
On my Mac Mini SoundSource (version 6) is working sometimes. It seems it – or the underlying ARK plugin – sometimes does not get fully loaded after booting the Mac. A restart almost always helps.
I’ve split this to a new thread, since it is very unlikely to have anything to do with the new laptop model, and more to do with your configuration (especially give how your two systems reproduce it).
As for what should be happening, nothing at all should happen if you click on the title bar, in the area where the project filename is printed (along with what you are editing inside the project). If you right-click, Cmd-click or Ctrl-click, then it will use the old system behaviour of showing the full path to the item in reverse order in a menu, that will cause Finder to load a folder of your choosing from that menu.
So to merely click upon the title bar should have no effect. Of course if you hold the mouse button down and move it, then it will move the window, but you’re probably in OS level code territory either way. I’m not sure if Scrivener has much at all to do with how the exterior of the window works, its frame, other than specifying that it shouldn’t show the miniature file manager that simpler single-document programs do, when using a modified click on the label, as described.
I was wondering if the OP meant the top item in the binder… which would try to display all sub documents if they were in Scrivenings mode… and if one of those docs is damaged… (or missing, due to sync?). Anyway… guessing.
I tried clicking the Draft Folder and the first item in the Binder there. Both separately and as scrivenings. I tried clicking on the project title. No issues. MB Pro ‘24 36 gig. I run far too many third party items. Perhaps a memory issue?
If I open other project that I have created I get no issue. It seams this project is the one causing the main issue. Which is strange in it self.
It is definitely a memory exception issue.
If I were a betting man I would tell you it is Apples fault. They changed something in Mac OSX 26.4
Now why it happens on two different devices is why I would think it is Apple.
I have sent the logs over to Literature and latte.
Thanks every one for all your attention to this issue.
Two different devices, but the same project? That points to something wrong with the project. Anyway, hopefully the bug report will help narrow down the issue! Understandably frustrating.
Thanks.
I have other projects I can work on.
The issue with this one is that it is the first time I include images with the project. I will take the TXT out and just write without the images. Not a huge issue.
Thanks to everyone for helping me out.
Have a super week everyone !
Have you tried the UI reset checklist yet on this project? That won’t necessarily solve a problem if an image format suddenly lost compatibility in the 26.4 update (to speculate), but it should at least clear the project so that it opens with nothing loaded rather than whatever it had loaded last, and halt the crash on load.
From there you can then test loading various sections to see if there is one in particular that is a problem, and go from there.
Amber thank you very much for all the help.
I have exported the work out as a TXT file without the images. I will create a new project with out images as this seams to be the major issue.
I appreciate all the help !
Let’s leave it here… No point at this time to keep going. It might just be mi project having a corrupt image or something else. It is not to much work moving things to a new file and I really don’t want to use support resources when it is just my project.
I supper appreciate all the help.
Thank you again and I love the product.
You guys should have a (send me a coffee) or it’s equivalent where I can donate more !
Keep up the good work.
Thank you for all your help.