Beta 026 crashes

Beta 026 crashed on me during use last night for the first time. I’ve been using it daily since it was released. It’s not something I can reproduce. Are crash reports automatically generated and sent to you guys?

Sorry to hear about your crash! Unfortunately, no, we don’t automatically get reports, but if you can paste in the one that Windows generated, that would be great. To get the report*:

  1. Open the Control Panel and choose Administrative Tools (under System and Security if you’re viewing categories)
  2. Open Computer Management
  3. In the tree view, select System Tools\Event Viewer\Windows Logs\Application
  4. In the window on the right, you should see a list of reports Information, Error, and Warning. Group these by date and sort by level, and then look for any errors that occurred at the time of your crash–the source column should say something like “Application Error” or “Application Hang”. Selecting any one should show you the details in the lower part of the window; you can also double click to open it in a new window. Make sure that “Scrivener.exe” is referenced in the description of the error, and then use the Copy button to send the contents to your clipboard (if you get an option, choose “copy details as text” rather than “copy table”).
  5. Paste the crash details in a post here, with your description of the crash.
  • These steps are for Windows 7; Vista and XP may be slightly different. In XP I believe the path in step 3 is just System Tools\Event Viewer\Application

If you could provide that along with your OS version and as much as you remember about what you were doing when you got the crash (splitting documents? dragging items in the binder? trying to view a group of documents as Scrivenings?) that would be quite helpful.

Ok thanks, I didn’t know about this. The crash report is attached. System is Win 7 Ultimate/SP1/x64. I was simply typing in one of the text frames when the crash occurred.
crash report.txt (1.66 KB)

Thanks, I’ve passed this on to Lee. If you get it again (which of course I hope you don’t!) please let me know. I’m afraid I don’t know of anything off the top of my head that would be related to just typing, so I don’t have any workarounds to suggest at the moment.

Thanks. Scrivener has been rock solid otherwise so I’m not too worried. I lost no more than a sentence or two because of the autosave.

Ok, it crashed again. :-/ This time I’m sure what I was doing when it crashed: nothing – I was literally just starting at Scrivener reading text; not moving the mouse, typing, scrolling, or anything else.

The new crash report is attached.
crash2.txt (1.66 KB)

Same thing is happening to me and only just started today. It has happened several times, giving the same error, except the “Faulting process id” is different each time.

Faulting application name: Scrivener.exe, version: 0.0.0.0, time stamp: 0x4e157094
Faulting module name: QtGui4.dll, version: 4.7.2.0, time stamp: 0x4e1504b3
Exception code: 0xc0000005
Fault offset: 0x0017d5d6
Faulting process id: 0x1098
Faulting application start time: 0x01cc527c25d2114f
Faulting application path: C:\Program Files (x86)\Scrivener\Scrivener.exe
Faulting module path: C:\Program Files (x86)\Scrivener\QtGui4.dll
Report Id: 9c3c4103-be8b-11e0-b4e8-0019b91dc2a3

Win 7 / Ultimate / x64

I wasn’t doing any special action, sometimes just typing or dragging text. Fortunately, no work has been lost.

I’m thinking of uninstalling and going back to 025 if possible.

before you do that, you might try making sure your machine has all recent Windows updates, and also restart it, then see if you get further crashes. since my last post in this thread, i’ve not had any more Scrivener crashes, so not sure if it’s something a recent Windows update fixed or not.

@deunde - I restarted a couple of times and tried different things, like making sure no other programs were running, etc. Still crashed. However, last night when I restarted it, nothing happened and I could use it as normal. So, I’ll see what happens today.

Well, since my last post I’ve used Scrivener for a full day and for a half day and had no problems at all.

Go figure.

I spoke too soon…

Faulting application name: Scrivener.exe, version: 0.0.0.0, time stamp: 0x4e157094
Faulting module name: QtGui4.dll, version: 4.7.2.0, time stamp: 0x4e1504b3
Exception code: 0xc0000005
Fault offset: 0x0017d5d6
Faulting process id: 0x17d0
Faulting application start time: 0x01cc55622e866d3b
Faulting application path: C:\Program Files (x86)\Scrivener\Scrivener.exe
Faulting module path: C:\Program Files (x86)\Scrivener\QtGui4.dll
Report Id: ec36e0e2-c16e-11e0-9e3f-0019b91dc2a3


In this case, I wasn’t doing anything in Scrivener. I had Scrivener open in the background and was watching a youtube video with Google Chrome. Then I clicked on Scrivener to start working in it, and at that point it crashed.

That’s Scrivener’s new No Goofing Off feature. If it detects you’ve been watching videos instead of writing, it punishes you when you return. :smiley:

026 just crashed on me for the first time. I had just edited “was enjoying this.” to “was actually enjoying this.”, and had then started rereading the paragraph. In other words, at the time of the crash, I was not doing anything.

Here’s the crash XML from 64-bit Vista:

- 1000 2 100 0x80000000000000 18105 Application foobar-PC - Scrivener.exe 0.0.0.0 4e157094 QtGui4.dll 4.7.2.0 4e1504b3 c0000005 0017d5d6 14bc 01cc55c51a06a0b0

When I brought the project back up and looked, the edit I had made immediately before the crash had been correctly auto-saved.

026 just crashed while I was working through the tutorial. I had just finished Step 14, and Scrivener crashed just after I selected Step 15 in the Binder. Upon restarting, I was able to access Step 15 without any trouble, though I hadn’t worked through the previous steps, so no other documents were open.

Crash log is attached - thanks!
crash08112011.txt (1.67 KB)

Thanks for the reports, all! Keeping Lee busy. :slight_smile:

I think this is the same bug, so I will append this crash info to this existing topic, but this event occurred on Beta 029.

I had just edited a sentence that began “He was surprised” to “He seemed surprised” and then seconds later (may have been more than the auto-save timeout, but I’m not sure), Scrivener crashed.

This does feel to me like a problem with auto-save, but I can’t be sure. Again, I’m pretty sure I was doing nothing except rereading my prose (no mouse clicks, no keyboard events, no UI input at all) when the crash occurred. I may have been moving the mouse, so the app may have been getting mouse events. I’ll try to be a little more observant if it happens again.

Faulting application Scrivener.exe, version 0.0.0.0, time stamp 0x4e4746db, faulting module QtGui4.dll, version 4.7.2.0, time stamp 0x4e40f047, exception code 0xc0000005, fault offset 0x0017d5b6, process id 0xc44, application start time 0x01cc5ab9ed9a5590.

This is the second time today Scrivener 029 has crashed on me. About 11 hours ago and just now. Same crash footprint.

This morning I had just altered one word of a text file and was rereading the paragraph when the crash occurred. Tonight I had just moved the insert cursor (mouse event) to begin a little change and was moving my hands to the keyboard when the program crashed.

Both times the crash was the same other than PID and start time.

Faulting application Scrivener.exe, version 0.0.0.0, time stamp 0x4e4746db, faulting module QtGui4.dll, version 4.7.2.0, time stamp 0x4e40f047, exception code 0xc0000005, fault offset 0x0017d5b6, process id 0x1a00, application start time 0x01cc5b59e0066450.

Just a thought, that all these crashes are occuring in the GUI module of the QT library that runs many things for Scrivener, and would be thought to be stable by itself as about a third of the world uses it (slight exaggeration).

This and the location might suggest that it could a problem with the screen driver in the Windows installation. Those kind of errors do tend to show up in this way also, kind of intermittent, show on window exposure or update (on text edit), etc…

jravan, on yours, I noticed the two fault reports appeared to be identical (timestamp), and that your location is just like the others except for a b6 where others have a d6 at the end (Fault offset: 0x0017d5d6). Is it possible this was a typo?

Hoping thoughts help.

Regards,
Clive

The data was cut-and-pasted, so no, I don’t think there was a typo. Looking again, I think the offsets are the same:

fault offset 0x0017d5b6, process id 0xc44,
fault offset 0x0017d5b6, process id 0x1a00,

Just crashed again while bringing the Scrivener window to the front.

Faulting application Scrivener.exe, version 0.0.0.0, time stamp 0x4e4746db, faulting module QtGui4.dll, version 4.7.2.0, time stamp 0x4e40f047, exception code 0xc0000005, fault offset 0x0017d5b6, process id 0xbec, application start time 0x01cc5bc0f44a5b80.