I’m thoroughly enjoying 2.0. Fast, responsive, versatile. A dream come true.
Unfortunately, I’m writing to report a crash by my brand-new first-day installation of Scrivener 2.0 (not the Nano installation). After about an hour of flawless performance, I backed up the project I was working on to a SanDisk USB memory stick. That backup went OK. But then I noticed I had not checked the box for a zip-backup. And so my next action was to attempt a zip backup of the project to the same memory stick. Crash.
At least a report was generated by Scrivener’s crash reporter (attached). I’m also attaching the automatic report that was generated for Apple since the end paragraph of that report includes information about the hardware involved.
The above took place on my MacBook Pro 2.33 GHz Core 2 Duo 10.4.11.
But no worries! Congratulations on this amazing release! I am in no way disappointed that there may be occasional bugs discovered during the first stages of intense public scrutiny. And it wouldn’t surprise me in the least to learn that a crash like this was caused by some oddity buried in my system. For example, I once accidentally threw this very memory stick into the washing machine (yikes), though it survived and has worked fine for at least a year of backing up zip copies of some of my Scrivener 1.51 projects.
Similar experience after instaling the 2.x. In the backup prefrence i checked for both backup on open and exit, resulted in crashs when quiting/close/exit…after some trying i ended up with un-checking the 3 backup choices on top of that pane…now it seems to close/exit ok…
The paid upgrade to S2 (5999) is also crashing on backups for me. I can perform one backup per “session” but after that the application crashes on every attempt to backup (Zip or not, Cmd-S forced or on exit)
This makes S2 totally unusable for me now. If I can’t backup during my working day then I can’t risk using it.
To repeat:
Open any project in S2 (5999)
Backup project
Backup project
I’m unfortunately having to move back to the NoMo release (5736) which doesn’t exhibit this problem for me.
Nothing changed in this regard since the NaNo release so I’m surprised there’s any difference. Thanks for the crash reports - I’m about to start going through them.
Scrivener isn’t crashing for me at all on backup though, so I haven’t been able to reproduce this yet.
If it helps, I’m backing up to a Dropbox/_WRITING BACK/Backups/ folder. But it still crashes if I change the folder. I’ve tried it with and without dropbox running, again no difference.
I’ve tried it with a clean blank project too, so it doesn’t sound like it’s an issue with my project.
I need to sift through the crash reports to get a better idea about what’s causing it. I’ll let you know as soon as I’ve gone through them - there are a lot to get through. That new automatic crash reporter I’ve put in is both a blessing and a curse: it’s great that I’ll now know about more crashes and so can work towards making Scrivener more stable than ever, but on the other hand ignorance was bliss.
