Crashes of late

I’ve had several crashes in the last 48 hours or so, both before and after the new update. Diagnostics attached. Just while doing very innocuous note input/edit sort of things.

Dorico (729.2 KB)

Your diagnostics contain a single crash report from today. The stack trace shown within is one we’ve seen before, but as yet we’ve been unable to figure out what’s causing the crash. If you have any clues about how to reproduce the problem, we’d be pleased to hear from you about it.

So, I had duplicated a selection to the staff below and I was going to then drop it down an octave. I’m not sure which action caused the crash.

The logs support this theory.

Last few lines from the application log

2024-01-18 17:59:08.846 [info] notifyPostCommandExecute: NoteInput.MIDINoteInput?MIDIPitches=42 (124 ms)
2024-01-18 17:59:09.601 [info] Posting command (requested): NoteInput.MIDINoteInput MIDIPitches=38
2024-01-18 17:59:09.607 [info] Executing command: NoteInput.MIDINoteInput?MIDIPitches=38
2024-01-18 17:59:09.734 [info] notifyPostCommandExecute: NoteInput.MIDINoteInput?MIDIPitches=38 (127 ms)
2024-01-18 17:59:12.152 [info] Posting command (requested): NoteInput.MIDINoteInput MIDIPitches=39
2024-01-18 17:59:12.158 [info] Executing command: NoteInput.MIDINoteInput?MIDIPitches=39
2024-01-18 17:59:12.285 [info] notifyPostCommandExecute: NoteInput.MIDINoteInput?MIDIPitches=39 (126 ms)
2024-01-18 17:59:16.692 [info] Executing command: NoteInput.Exit
2024-01-18 17:59:16.709 [info] addEventsForAudition() adding 1 events to buffer #:0
2024-01-18 17:59:16.714 [info] notifyPostCommandExecute: NoteInput.Exit (22 ms)
2024-01-18 17:59:16.714 [info] processAuditionEvents() - processed 1 events
2024-01-18 17:59:24.313 [info] Posting command (requested): Edit.SelectAtPoint X=3958, Y=217.5, AddToSelection=0, BlockSelection=0, NextSelectionAtPoint=0, SelectionTriggerAction=0, OpenScoreID=0
2024-01-18 17:59:24.314 [info] Executing command: Edit.SelectAtPoint?X=3958&Y=217.5&AddToSelection=0&BlockSelection=0&NextSelectionAtPoint=0&SelectionTriggerAction=0&OpenScoreID=0
2024-01-18 17:59:24.370 [info] addEventsForAudition() adding 1 events to buffer #:0
2024-01-18 17:59:24.371 [info] addEventsForAudition() adding 6 events to buffer #:1
2024-01-18 17:59:24.374 [info] processAuditionEvents() - processed 7 events
2024-01-18 17:59:24.391 [info] notifyPostCommandExecute: Edit.SelectAtPoint?X=3958&Y=217.5&AddToSelection=0&BlockSelection=0&NextSelectionAtPoint=0&SelectionTriggerAction=0&OpenScoreID=0 (77 ms)
2024-01-18 17:59:25.763 [info] Executing command: Edit.SelectAtPoint?X=3903.5&Y=218.5&AddToSelection=0&BlockSelection=0&NextSelectionAtPoint=0&SelectionTriggerAction=1&OpenScoreID=0
2024-01-18 17:59:25.820 [info] addEventsForAudition() adding 1 events to buffer #:0
2024-01-18 17:59:25.821 [info] addEventsForAudition() adding 6 events to buffer #:1
2024-01-18 17:59:25.840 [info] notifyPostCommandExecute: Edit.SelectAtPoint?X=3903.5&Y=218.5&AddToSelection=0&BlockSelection=0&NextSelectionAtPoint=0&SelectionTriggerAction=1&OpenScoreID=0 (77 ms)

and then the crash at:

Date/Time: 2024-01-18 17:59:25.8720 -0500
OS Version: macOS 14.2.1 (23C71)
Report Version: 12
Anonymous UUID: DD7D6634-4C1F-B977-EE30-1D58C0306D61

Time Awake Since Boot: 220000 seconds

System Integrity Protection: enabled

Crashed Thread: 0 Dispatch queue:

Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000
Exception Codes: 0x0000000000000001, 0x0000000000000000

Termination Reason: Namespace SIGNAL, Code 11 Segmentation fault: 11
Terminating Process: exc handler [78879]

VM Region Info: 0 is not in any region. Bytes before following region: 4305272832

If i’m reading that right it looks like it’s getting a null pointer and not checking for it.

If you’re able to reproduce this, that would be great. Unfortunately, in general, making selections doesn’t cause the crash, and we’ve gone over the suspect functions with a fine tooth comb looking for weaknesses where the state might not be what we expect and require, but haven’t so far found the problem.

Just had another one. I crashed while I was dragging the score around to pan.
Dorico (702.4 KB)

And again

Dorico (756.9 KB)

This is happening wit concerning regularity since the most recent patch.

And again.

Something is rotten in Denmark @dspreadbury. I’d had the very occasional crash since 5.0, but nothing like this last week or so.
Dorico (750.8 KB)

I’m sorry that you’re getting this crash often. Can you describe with any greater clarity what steps you are taking immediately before the crash?

I’ve had similar recent increase in non-reproducable issues/crashes. I suspect it is related to the VST I have associated with the project/track… but since it is not readily reproducible… it’s only a guess. I previously sent logs and always send the auto/anonymous reports… so hopefully that eventually helps lead to something.

and again
Dorico (738.5 KB)

The common factor I’ve noticed is that it seems to happen when trying to make a selection after doing some amount of midi note input.

Still happening, more frequently if anything. Three crashes in my

One thing I have narrowed it down to is that it involves the mouse in some way.

At this point it is extremely hard for me to work Dorico because of constant crash anxiety. Frequent autosaves only help so much, and have their own tax on a large project.
Dorico (806.3 KB)

This crash has been encountered by a lot of users and is a high priority for us to fix. It’s a really difficult one because there is a timing element to it, which instantly makes it harder to reproduce. We have added some extra protections in the relevant area and hope this will be enough to fix the crash, even though we cannot reproduce it on demand.

I have also had a ton of crashes lately - there seems to be no rhyme or reason - just doing simple stuff. Tried to upload my diagnostic zip but it was too big, even when I deleted every file but one. Thanks for any illumination…

Hi @lindascott121 and welcome back to the Forum.

You could upload the zip file with diagnostics on some Cloud service and post the link here.

Linda, you can send your diagnostics to me directly by email at d dot spreadbury at steinberg dot de. We’ll be pleased to take a look and see if we can figure out what’s going on.

OK . I have narrowed it down, somewhat - it has to do with the surface pen use -only when I am using that does it crash. Thanks.
link to diagnotics zip file:


Thanks for sending the diagnostics, Linda. I have an idea how to help you – I’ll send you a direct message.