Dorico 5 crash

Dorico
1

I don’t know if this is the proper forum for reporting a crash. Guide me if it isn’t.

I’m using Dorico 5. I had two different projects open, both of they using the Aria player. I was looking at project A with that as my Windows focus. In project B I was in write and had they keyboard open in the bottom panel. With project A having the Windows focus I clicked on a key in B’s keyboard. Windows said B was “not responding.” I tried to do something in A and that became “not responding.” I used the Windows task manager to kill it all. I tried restarting Dorico and was told it could not establish connection with Aria (I didn’t record the exact text of that message). I waited a couple minutes and Dorico restarted.

While my primary purpose is to report the crash, some guidance in getting to autosaves would be appreciated.

2

Upload your Diagnostics.
(Do Help>Create Diagnostic Report and upload the zip file that appears on your desktop)

3

Dorico Diagnostics.zip (972.0 KB)

4

It crashed again. This time I had been working in project B, closed the project A window, then closed project B. But instead of closing I got “not responding.”

I started Dorico to get the crash report, but it wouldn’t start because of no connection to Aria. I waited a while (as I typed this note) and tried again. This time I was able to see the “warning message”:

image
image452×289 19.8 KB

I clicked on Terminate. This time it gave me the Dorico Diagnostic zip file.

Dorico Diagnostics.zip (960.0 KB)

5

… gave me the zip file without me actually requesting it.

6

Hi @bellist , yes, here is a good place to report crashes.
Interestingly though, the diagnostic report contains no crash dumps, but only 2 freezedumps of the VSTAudioEngine (that’s the one that actually loads Aria) of zero size. So that does not help me any further.
Could you please do following instead when you run into that situation again?

  • Get the free utility Process Explorer from here. It’s tiny, less than 3.5 MB
  • When Dorico “crashes” again start Process Explorer (procexp64.exe) and have a look for the process called VSTAudioEngine.
  • Highlight that VSTAudioEngine and do a right click on it, from the pop-up menu choose Create dump > Create mini dump.
  • Though it’s called mini dump, it’s still quite large, so please zip it up and post here.
  • Would be even best, if you could create 2 mini dumps in a row, so I can see if the audio engine is really hanging in the same spot.
  • And additionally please also create another diagnostic report at that time.
    Thanks a lot
7

Of course, today, when I’m specifically trying to make it fail, it works just fine.

The process explorer is downloaded and ready for whenever.

8

Took a while before it failed. I think I zipped it right (not having done it before). A 19Mb dump file came out as a 4.9Kb zip folder. But that’s still to big to upload when the limit is 4Kb.

9

You can send the file directly to @Ulf to his email address:
u dot stoermer at steinberg dot de
reference this thread.

10

Here’s the Dorico Diagnostics of the failure. I could only generate it after Dorico failed to restart.

Dorico Diagnostics.zip (823.7 KB)

11

Dump file emailed.

12

Thanks for the dump file. It clearly shows the audio engine being deadlocked, i.e. the main thread is waiting for a signal from another thread that never comes. When the main thread is stuck it also can not communicate with Dorico any more and therefore also Dorico gets stuck as well.
Unfortunately, from the dump I can not tell what is causing the deadlocks and whether it is related to ARIA player or not. Would be also interesting to see if Dorico 6 behaves the same.

And coming back to your question about Auto Save. I think Auto Save is switched on by default and you can configure it by means of the Dorico preferences dialog. There you go to the General tab and then the Files sub-tab.