I did an uninstall of 2,9.9.12 64 bit, cleaned up some extra stuff (old uninstalls that aren’t valid) with CCleaner, and did a reinstall of RC 12. It was asking me to do the initial setup stuff, like Backup forlders. But I didn’t get too far before it crashed. I haven’t timed it, but roughly 17 sec.
I installed RC 13 a bit ago, and am not seeing any change. I haven’t been writing, so I’ll forgo trying the 32 bit to see if I can do something to help. What would be the most useful for you right now? Would a log help?
If you still experience the crash upon Help > Check for Updates, please generate a log file file running ScrivenerLog.bat (with Admin rights) and attach the generated log file to this thread. The log file is generated within the “logs” subfolder. Copy paste from the console output will do the job too. Thanks!
Installed the 64 Bit version. Crashed in usual time frame - presumably checking for automatic update. I didn’t have a chance to change that setting before running. I’ll perform more testing and generate a log tomorrow - I’ve got other stuff to do right now.
The .bat file didn’t work, but I started Scrivener invoking “–log.” I didn’t see anything interesting, although it slowed my computer waaaaaaaaaaaaaaay down after I checked for an update. (I’ve got 16GB of RAM and a Ryzen 5…Scrivener shouldn’t be hanging my system.)
Just run and got log file. These are the last few lines. You are welcome to the whole thing if you need it but I guss it tells you how far Scrivener got before closing.
Info: No PostScript name for family: “Yu Gothic UI Light”
Info: No PostScript name for family: “Microsoft JhengHei UI”
Warning: No voice found for given locale
Debug: Checking network connection.
Debug: Checking network connection.
Debug: Update about to start.
Just ran another test with log on. This time I disabled automatic check for updates before opening Scrivener with logging on. I then went into Help and selected “Check for Updates”. Scrivener closed immediately. Last line of the log reads the same as my previous post: “Update about to start”.
Yeeeeahhhh… Downloaded that latest build in 64-bit, tried running it to disable the automatic update check and run a log for you guys… it won’t even stay open long enough for me to get the automatic update thing changed.
Going back to the 32-bit version, for now. That’s working…
Takirks, if you disconnect from the internet you should be able to open scrivener and turn off the automatic update check. That’s what I’ve had to do. All the best Simon
If you still experience the crash upon Help > Check for Updates, please generate a log file file running ScrivenerLog.bat (with Admin rights) and attach the generated log file to this thread. The log file is generated within the “log” subfolder. Copy paste from the console output will do the job too.
This build also generates coredump files, which will allow us to trace in greater detail what is going on under the hood and what fails exactly. After you experience the crash a *.dmp file is created within the “minidump” subfolder of Scrivener. Please, upload in this thread the last *.dmp file generated within this folder or email it to tiho at literatureandlatte dot com. You can also share the *.dmp files via Dropbox, if they are too big. You MUST run Scrivener as Administrator to generate the DMP crash file, so right-click Scrivener and choose “Run as Administrator”.
I believe this will be the last set of installers and we will be able to pinpoint the problem with this build, once we get the new logs and *.dmp files.
I can confirm that it seems to be related to updates as well. I put my computer in Airplane mode, got into Scriviener just fine. I turned off Automatic Updates and am able to reopen it with no shutdown. As soon as I told it to do a check for Updates, it crashed. I ran another with logging, opened my project, and did another update. I’ve attached that log file for you.
Thanks for all the hard work on this! Happy Holidays!
Thank You all for the logs and the mini dump files, guys. They helped us a lot.
The problem is caused by a change inside the Qt Library. Qt already have a bug report related to this problem. We do not know when it will be fixed, but will do our best to trace the problem further and find a solution.
Until this problem is solved, I am afraid you will have to disable auto-update and update Scrivener manually using the full installers (if you are using the HighDPI version of Scrivener with Qt 5.15.2), or use the Non-HighDPI version of Scrivener which uses an older version of Qt 5.12.9 and does not have this problem. If you are using the Non-HighDPI version, please have in mind that you will have to upgrade manually using the full installers to the Non-HighDPI version next time too, as the Auto-Update will download and install the HighDPI version automatically.
Never had this problem, but I think newest versions of Qt need some of that myriad of MS’s runtimes we need to run ANYTHING under Windows. I have a lot of them on my PC, so Scrivener runs fine without crashing upon update check. (Just an hypothesis, though.)
@tiho_d
Did you try to compile Scrivener under the new Qt 6.0 that came out a few days ago? Maybe they solved the problem in that version.
Using Qt 6 is not on our radar at the moment. We will consider it for an official release once Qt 6.1 is out probably.
Qt has acknowledged the bug and the bug is open within their bug tracking system and there is no solution, bug fix or workaround proposed. It has to do with some computer network configurations, but not clear exactly what is causing it. We and Qt know exactly where the crash happens but not clear why crashes on some computers only.
@ The guys who are experiencing this crash: Do you run Scrivener under Wine, or do you have anything Linux related when you run Scrivener and experience the crash? The bug was initially reported as a Linux only bug, but Scrivener for Windows crashes exactly at the same place as reported in the Qt bug with the same symptoms described in the Qt bug tracking system.