I read this thread with interest because my PC crashed twice today while I was using Scrivener. The blue screen of death appeared, reporting “PAGE FAULT IN NONPAGED AREA” Is this the sort of error caused when the 2GB limit of 32 bit software is reached?
I checked the memory usage of Scrivener via Task Manager and notice that it creeps up by about after each ‘search’ where I then select all the documents found and revue them in Scrivener mode. Is this what you refer to as “memory leakage”?
I saw it go up from 222.8MB when I first opened Scrivener to 299.6MB after doing the process described below.
I can repeatedly make Scrivener crash by doing search, then putting into Scrivener mode. Here’s some background to how I can make it do this…
If I use a common word like “a” as the text to search for Scrivener shows up all the documents found OK.
But if I then select all the documents found I can watch in Task Manager as the memory used by Scrivener creeps up towards 2GB.
The first time I do this memory usage went up to 1,741.5MB.
If I repeat the process, and memory usage hits the 2GB limit, Scrivener simple vanishes - as if I’ve shut it down. i.e. Scrivener crashes. This didn’t crash the whole PC to the blue screen of death as described above. It just crashed Scrivener, so I still can’t be sure if it is Scrivener that is causing the more serious blue screen problem.
My ability to crash Scrivener, as described above is easily repeatable.
I love Scrivener. Scrivener has been invaluable in writing my books. I just hope that this book doesn’t outgrow Scrivener’s capabilities.
