So, I was using the NANO version for a week without a single glitch.
Not one.
I then paid for my upgrade and installed the 2.0 full version.
Tragically, Scrivener now crashes each and every time a single window is closed. In other words, the moment a project is closed, it crashes. When I start up again, it suddenly uses up to 2GB of memory and vast CPU resources to prepare a crash report, something I did not ask for it to do…
If I try to go back and use the NANO version, I am told “Project Already Open”.
Really disappointed.
Steps to reproduce crash:
Start Scrivener (assume this is a clean start without the three minutes of crash reporting that locks my whole machine up)
create a brand new document, using the blank template.
Save the project.
Attempt to close the project
RESULT: CRASH
Alternate steps:
Start Scrivener (assume this is a clean start with th three minutes of crash reporting that locks my whole machine up)
Load previously created project.
Save the project.
Attempt to close the project
RESULT: CRASH
My new coveted tool is now useless to me.
I am sad.
I uninstalled all versions using AppZapper (is there nothing it can’t do?) and then re-installed 2.0
All is good.
It no longer crashes on exit or on closure of projects.
Happy, Happy, Joy, Joy
(now if someone would explain to me how to make the paper transparent in full screen mode when using a background image, well, that would be just super…)
I had the same problem yesterday. Quit and nothing happened. I forced quit and sent the report. But I just quit and everything worked as expected.
Astounding update, I love the new footnotes mode.
I experienced the same issue yesterday and filled out the crash report that popped up. I neglected to mention in the report that I had created the project in the NaNoWriMo pre-release of Scriv 2.0 however. That might be relevant.
Thanks for sending the crash reports (and for the kind words). I have 400 to go through (down to just over 200 now), so I won’t be able to get back to them all personally, but I do appreciate your sending them to me. (I hasten to add that there aren’t 400 different crashing bugs - there seem to be three or four main ones at the moment, then a couple of other obscure ones and a couple relating to updates). I’ll be going through every single one…
Thanks again,
Keith
I didn’t send it as I was not yet sure that it was in fact not my fault.
And in a way it was.
I had both the NAMO version and the new version, which I had installed upon 1.0
No doubt, this was not expected as an ideal install
uninstalling all and reinstalling did the trick.
should have sent the crash report anyway.
my bad