[JH] Bug: Scrivener issues "Scrivener is Not Responding."

[dlt123me]

I am running Version: 2.9.0.2 Beta (50498) 64-bit - 21 Dec 2017, on a Windows 7 64bit system running 32 GB ram.

When I run the tutorial or even if I create a new project, if I click on anything in the Application it causes W7 to display "Scrivener is Not Responding." Something is definitely not working. I cannot do anything in this Beta...

I am running Eset Security System Antivirus and Malwarebytes on my system... Both have been disabled and still am not able to do anything in the Beta of Scrivener...

I should also add... that at times it will finally respond, but the wait is unacceptable. Others have mentioned this as well.

[setherd]

I had a similar issue and it was a bad hard drive

[dlt123me]

I had a similar issue and it was a bad hard drive

That would make sense since something must have been stored on a corrupted portion of your drive. As for my system, my drives are fine, but the software is very sluggish as others have mentioned in their posts.

I really look forward to V3 being released...

[jandrewnelson]

I've run into the same problem as well -- but no hard drive issues. New laptop and all my diagnostics say the HD is working great.

I did see a suggestion somewhere to change the frequency of auto-save/backup and it seemed to help, but not enough. The "Scrivener Not Responding" error is frustrating and may qualify my laptop for the first launched into space from South America.

Jerry Nelson
Buenos Aires

[MimeticMouton]

If you boot Windows into Safe Mode with Networking, are you able to run Scrivener without the lag there? Given that this is occurring in a new blank project (if I understand correctly), it may be the delay is coming from interaction with other software installed on the system, and testing in Safe Mode will reduce a measure of that.

[jandrewnelson]

[quote="MimeticMouton" Given that this is occurring in a new blank project (if I understand correctly)[/quote]

I don't know about others, but in my case, you do not understand. I get the 'not responding error' frequently and randomly while I'm working on a project. Not just once. Not upon start-up, but many times WHILE I'M WRITING ON A PROJECT.

[MimeticMouton]

@jandrewnelson - You're right, I was responding to the OP's comment of the freezing happening even in a new project, and perhaps I was misremembering from another thread about clicking in the project. If your issue isn't the same, we could use more details on it. Does the hanging only happen in the one project? How large is the project where you're seeing the freezing and what's the average size of the documents you're working in when you get the freezing? What actions trigger the "not responding" message?

[jandrewnelson]

Scrivener stops responding randomly with no duplicatable steps. It stops in different projects, but not all and when it stops responding, it may go into hibernation for an hour or just a few minutes.

I will say though that the non-responsiveness has decreased since I first noticed this thread. It's almost as if someone may have fixed the issue?

Thanks!
Jerry Nelson

[MimeticMouton]

I will say though that the non-responsiveness has decreased since I first noticed this thread. It's almost as if someone may have fixed the issue?

Hmm, in that case you might take a look at what's changed or updated on your computer, as there's no change in Scrivener itself (assuming you've been running 2.9.0.2 the whole time)--we can't make remote changes or anything of that sort; the software is installed locally on your machine and must be manually updated. But there could be a difference in what other programs you have running in the background, or Windows may have performed an update at some point, which could certainly affect things.

[jandrewnelson]

I'm not a computer guy at all, but I did hear something about Windows doing an update. I wonder if that may have caused something?

Thanks for the help though -- we'll get to the bottom of this!

[msackeygh]

I've had this bug since the first time I downloaded the beta version of Scrivener 3 which I think was 2 months ago (?). The latest version also has that bug.

The way I recover from this is to have Wnidows close the program and usually reopening Scrivener solves that problem for that instance. It seems rather random when this problem occurs. It doesn't occur each time I open Scrivener.