Crash reporter crashing Scrivener

This is troubling… when I launched Scrivener it brought up the Crash Reporter window… only I don’t recall it having crashed last time I had it open. I get the spinning beachball, and then the crash reporter and Scrivener crash again. I see the Template Chooser behind the CR window, so I don’t think it’s trying to open a project, but I could be wrong…

From the Console output with a “Scrivener” search term:

11/22/13 2:08:45.401 PM Scrivener[29612]: Scrivener(29612,0xa0ed51a8) malloc: *** mach_vm_map(size=8388608) failed (error code=3)
*** error: can’t allocate region
*** set a breakpoint in malloc_error_break to debug
11/22/13 2:08:45.404 PM Scrivener[29612]: Scrivener(29612,0xa0ed51a8) malloc: *** mach_vm_map(size=8388608) failed (error code=3)
*** error: can’t allocate region
*** set a breakpoint in malloc_error_break to debug
11/22/13 2:08:45.466 PM Scrivener[29612]: Scrivener(29612,0xb029b000) malloc: *** mach_vm_map(size=8388608) failed (error code=3)
*** error: can’t allocate region
*** set a breakpoint in malloc_error_break to debug
11/22/13 2:08:45.467 PM Scrivener[29612]: Scrivener(29612,0xb029b000) malloc: *** mach_vm_map(size=8388608) failed (error code=3)
*** error: can’t allocate region
*** set a breakpoint in malloc_error_break to debug
11/22/13 2:08:45.467 PM Scrivener[29612]: Scrivener(29612,0xb029b000) malloc: *** mach_vm_map(size=8388608) failed (error code=3)
*** error: can’t allocate region
*** set a breakpoint in malloc_error_break to debug
11/22/13 2:08:45.467 PM Scrivener[29612]: Scrivener(29612,0xb029b000) malloc: *** mach_vm_map(size=8388608) failed (error code=3)
*** error: can’t allocate region
*** set a breakpoint in malloc_error_break to debug
11/22/13 2:08:45.467 PM Scrivener[29612]: -[NSPersistentUIWindowSnapshotter writeWindowSnapshot:length:width:height:bytesPerRow:toFile:inDirectory:encryptingWithKey:uuid:checksum:isUserWaitingImpatientlyForThisThingToFinish:]: deflateInit(&strm, compressionLevel) returned Zlib error -4 on line 698
11/22/13 2:08:45.468 PM Scrivener[29612]: Scrivener(29612,0xb029b000) malloc: *** mach_vm_map(size=8388608) failed (error code=3)
*** error: can’t allocate region
*** set a breakpoint in malloc_error_break to debug
11/22/13 2:08:45.468 PM Scrivener[29612]: Scrivener(29612,0xb029b000) malloc: *** mach_vm_map(size=8388608) failed (error code=3)
*** error: can’t allocate region
*** set a breakpoint in malloc_error_break to debug
11/22/13 2:08:45.468 PM Scrivener[29612]: Scrivener(29612,0xb029b000) malloc: *** mach_vm_map(size=8388608) failed (error code=3)
*** error: can’t allocate region
*** set a breakpoint in malloc_error_break to debug
11/22/13 2:08:45.468 PM Scrivener[29612]: Scrivener(29612,0xb029b000) malloc: *** mach_vm_map(size=8388608) failed (error code=3)
*** error: can’t allocate region
*** set a breakpoint in malloc_error_break to debug
11/22/13 2:08:45.468 PM Scrivener[29612]: -[NSPersistentUIWindowSnapshotter writeWindowSnapshot:length:width:height:bytesPerRow:toFile:inDirectory:encryptingWithKey:uuid:checksum:isUserWaitingImpatientlyForThisThingToFinish:]: deflateInit(&strm, compressionLevel) returned Zlib error -4 on line 788
11/22/13 2:09:11.058 PM Scrivener[29612]: Scrivener(29612,0xa0ed51a8) malloc: *** mach_vm_map(size=8388608) failed (error code=3)
*** error: can’t allocate region
*** set a breakpoint in malloc_error_break to debug
11/22/13 2:09:11.060 PM Scrivener[29612]: Scrivener(29612,0xa0ed51a8) malloc: *** mach_vm_map(size=8388608) failed (error code=3)
*** error: can’t allocate region
*** set a breakpoint in malloc_error_break to debug
11/22/13 2:09:11.068 PM Scrivener[29612]: Scrivener(29612,0xb04b4000) malloc: *** mach_vm_map(size=8388608) failed (error code=3)
*** error: can’t allocate region
*** set a breakpoint in malloc_error_break to debug
11/22/13 2:09:12.383 PM com.apple.launchd.peruser.501[142]: (com.literatureandlatte.scrivener2.32064[29612]) Job appears to have crashed: Bus error: 10
11/22/13 2:09:12.413 PM ReportCrash[29641]: Saved crash report for Scrivener[29612] version 2.5 (2.5) to /Users/rguthrie/Library/Logs/DiagnosticReports/Scrivener_2013-11-22-140912_Simon.crash

Do you want the Scrivener*.crash log too?

P.S. Note that I wouldn’t be surprised if this is a Mavericks bug. I’ve been getting frequent crashes from Twitterific since the upgrade too.

Someone else reported the crash reporter crashing Scrivener while Mavericks was in beta, but I’ve never been able to reproduce - I did some testing following that report, and the crash reporter seems to work fine for me.

That’s a weird one, as it’s just saying that it can’t allocate memory. Try the usual - clearing out your preferences - and see if that helps. Otherwise you can always delete the crash log from ~/Library/Logs/DiagnosticReports to prevent the crash reporter from appearing.

All the best,
Keith

I recently (just a couple of hours ago) exported my preferences and then re-imported them. I was able to exit and restart Scrivener with and without loading a few different projects, all without crashes. Crossing my fingers that it was as simple as that.

Update: After having my project open for a number of hours working on it, I closed it down, let it perform an automatic backup, and then started it back up; no crash or crash reporter. Exporting & re-importing my preferences seems to have worked… crossing my fingers that this will continue to prove true.

Glad you’re up and running at least, although it’s strange this has happened - let me know if you run into it again.
Thanks,
Keith

Sad news: I just launched Scrivener. I brought up the template chooser, and then the crash reporter window on top of that. The CR window again refused to accept my input, and eventually it and Scrivener crashed. I relaunched scrivener, got the crash reporter, and was abel to edit the text window, but it failed with the message “Could not submit crash report. The request timed out.”. Not the first time this has happened.

I’m going to reset my preferences this time, and see if that fixes the issue, but I’m not seeing anything that looks like a crash when I quit Scrivener, and besides that, how would my preference settings cause the crash reporter itself to fail? If you want me to dig around in my Library for crash logs, let me know.

Hopefully, this will be the last update to this situation…

Two sessions in, and the complete preferences reset seems to have done the trick. No more crashing crash reporter. No crashing at all, actually. Also, it seems that before the rest, my inspector synopsis didn’t reflect the Label color, but now it does (I have that feature turned on for the cork board). Seems as if I’ve accumulated some preferences errors along the way.

Having a similar problem like robertdguthrie. The second crash within 24 hours and I am a anxious to continue using Scrivener. I lost some of my writings.

Just before Christmas I had to buy a new MacBook Pro with Mavericks. Updated everything. Scrivener: 2.5 (25236) (from App Store)

Yesterday, when I started with the real work on Scrivener, it chrashed afte about an hour when I switched from Scrivener to look a PDF file in the background. When I switched back, Scrivener crashed showing the chrash reporter.

After starting up the Mac and Scrivener and tried to repeat the switching, it crashed again. Now I am afraid to switch from Scivener to another programm or to call another program via the dock while working with Scrivener. It is quite awful.

This morning I started with Scrivener again, but is did not open at all, just showing the crash reporter. When starting Scrivener again, it came up. However, when shutting down the Mac totall and starting again, Scrivener crashed again, but ran when I restarted Scrivener.

I am now very anxious to use Scrivener, which is per se a fine programme for a writer like me and it worked find on my older Mac since I bought Scrivener 2 years ago. But as I am in a final phase of a project and have a deadline with my publisher, I am now transferring all files to NeoOffice. Quite laborious, and not comfortable – apart from the additional hours I have to spend just to fix technical problems.

If I can do something to repair this bug, please describe it in simple words. I am not a computer specialist, only just a simple writer with laymen’s knowledge of computers.

Or even better: If the hack, you may propose it too complicated, please provide me with a totally new DMG-file.

Attached is the protocoll of the first crash yesterday. For the crashes from this morning, the crash reporter did not save a protocoll (at least: I cannot find any).