Ctrl/Cmd A in a large score = Crash

I made the grave mistake of accidentally hitting Ctrl+A in score with 500 bars. After ~5 minutes of Dorico hanging trying to execute it, the app crashed.

Why is this action so resource intensive?

Can you please do Help > Create Diagnostic Report and attach the resulting zip file here so we can take a look at the crash log?

Making large selections in Dorico is indeed quite resource-intensive because of the way the detailed data about selections is collected and processed. It’s certainly something we would like to improve, and some work in this area was done during the Dorico 4.0 development cycle but not completed due to other competing priorities. You can certainly expect us to return to this in future.

1 Like

The report is too large to attach here. Where can I sent it?

You can email it to me at d dot spreadbury at steinberg dot de.

1 Like