I have been experiencing a lot of crashes in the past few days. Inevitably, when I close the program, it crashes, and sometimes when I save a document.
I’ve attached a crash log if that might help the team to find an answer,
Thanks for the data, Benoit, we will have a look.
But have you also seen crash reports of the VSTAudioEngine? In case of doubt, simply do from the menu Help > Create Diagnostics Report, that will grab everything that is relevant for us to be watching at.
@dspreadbury , the Dorico ips files I uploaded to TST-6713.
All of the crash logs in the diagnostic report show the same stack trace. It looks like Dorico is crashing when trying to show the Hub window after you have closed a project. The crash suggests that we’re trying to set the keyboard focus somewhere in one of the controls in the window, and that this is failing somehow. We don’t explicitly try to force keyboard focus to a specific control in the Hub, so I’m unsure what might be going on here.
Do you have any unusual keyboard settings on your computer? Are you running any third-party utilities that might interfere with the input method on your computer, e.g. auto-completion tools or anything of that nature? Are you running with an unusual input method chosen (under Text Input in the Keyboard pane of System Settings)? Do you have any unusual settings activated on the Accessibility pane of System Settings?
Thank you Daniel,
is there something I can delete (preferences of some sort) or re installing something since I did not make any change to my gear or applications in months?
If this is a new phenomenon, there must be some kind of configuration change on your system that’s triggering the problem. Can you answer any of the questions I asked in my previous reply concerning your system settings, third party utilities, etc.?
Dorico keeps crashing. I accidentally opened a new project; ctrl+n instead of shift+n. When I tried to discard the new project it took the whole program down. This has happened multiple times
Then it’s probably best next time it does this to do the Help > Create Diagnostics Report thing so someone from the Steinberg team can advise (zip it and upload here) or this.
Dorico crashes under any and all types of circumstances! I’m simply trying to print parts but it crashes just clicking on the Print tab. I keep dutifully sending the crash reports in but nobody seems to notice or care.
You’ve sent a link to Google Drive that requires specific access to be granted. Please instead try sending the diagnostics to me via a service like WeTransfer.com (it’s free). My email address is d dot spreadbury at steinberg dot de.
Thanks for sending the diagnostics. All of the crashes show a consistent call stack, which is good on one level: it suggests there’s a single problem, which hopefully we’ll be able to resolve.
The crash is deep in the Qt application framework that Dorico is built on. I will ask my colleagues whether they have any ideas about what might be going on.
In the meantime, could you try temporarily disabling Avast antivirus on your computer? It’s the only slightly unusual DLL that I can spot in the list of modules loaded on your system while Dorico is running. If disabling it makes no difference, please try temporarily uninstalling it; if you’re worried about leaving your computer unprotected for a short while, enable Microsoft Defender, which is built in to Windows, instead: Defender is typically all you need to protect your computer from viruses and malware, and certainly doesn’t interfere with Dorico.
Thanks for the updated set of diagnostics. There were three crash dumps in the latest set, two of which were older ones that still showed Avast being loaded, and one of which looked like it was a brand new one where Avast was not loaded. Unfortunately, that crash log shows the same symptoms as the previous ones, so that indicates that Avast is not solely responsible for the problem you’re experiencing.
If Dorico crashes on start-up, if you wait a few seconds, are you then able to restart the application and have it start successfully, or do you have to take specific steps to get back up and running?
It doesn’t typically crash on startup. It usually happens in the middle of the workflow. I can’t really pinpoint a specific action that initiates the crash. Not even the accidental opening of a new document does it consistently. I do think the removal of Avast from the computer has improved things quite a lot. I have transferred the latest diagnostics report to you. I appreciate your help.