Literally Cannot Continue on Project due to Crashes

Dorico crashed while I was working on a project. I reopened it, and it crashed again. I can’t work on it for 30 seconds before it crashes again – my Dorico is now useless, at least on this project I’ve spent hours on. Can anyone help? I have a diagnostic report, but the forum says it exceeds the maximum size for uploading, so I can’t attach it. BTW, yes, I rebooted … it continues to crash on this project. Help!

Can you give more details about your configuration, or even attach the file concerned (or the crash report) ? this will help members to help you effectively.

1 Like

Do you have loads of third-party VSTs…? That’s the usual culprit.

Can you provide a link to Dropbox or OneDrive of the report, for the devs?

2 Likes

Configuration: using MacOS Sequoia 15.5 on a Mac mini with M4 Pro. Dorico version 6.0.10.6032.

As mentioned:

I have a diagnostic report, but the forum says it exceeds the maximum size for uploading, so I can’t attach it.

So there’s that. Let’s see if the Dorico file is small enough to attach.
71_Nature Boy.dorico (4.0 MB)

Do you have loads of third-party VSTs…?

No idea what that even is, sorry.

Can you provide a link to Dropbox or OneDrive of the report, for the devs?

Erm … I think I made a Dropbox account years ago. Let me see if I still have access.

If I did it right, here’s a link to the diagnostic file on Dropbox:

Thanks, I will check in about 2.5 hours

@1941house, is the problem that Dorico is crashing during chord symbol input?

Looking at the log files, I get the same impression…

Yes, during chord input.

BTW, don’t look too hard at the Dorico file I attached (Nature Boy) because my Dorico just crashed on a completely separate project … while entering chord symbols. So I don’t feel it’s specifically related to that score, but more an overall Dorico problem with chord entry.

Indeed, we are on the tail of this problem. There’s a timing-related bug, which shows up a lot on some computers but not at all (or at least very infrequently) on others. Try not to whizz too quickly through chord symbol input, e.g. don’t hit Space or Tab or otherwise move the popover from position to position very fast, and you should find that the program behaves better. The same problem will affect lyrics, fingering, and figured bass input too.

We are working on a fix for this problem and will have it with you as soon as possible. I’m very sorry for the inconvenience caused in the meantime.

1 Like

Thank you – with this information, I can, at least, continue working. I look forward to a resolution. Thanks again for looking into this.