Crashes in Inspector when selecting note elements

• Jan 3, 2014 - 23:41
Type
Functional
Severity
S2 - Critical
Status
closed
Project
MuseScore

Windows 7, GIT commit: d6d0b1a

Playing with the Inspector with a note selected, I am running into lots of crashes. I am not sure I have a handle on all of what I am seeing, but either of the following seems to crash for me reliably:

* click notehead of a beamed note, click the Beam button at bottom of Inspector

or

* click notehead, click Stem button at bottom of Inspector

I've also seen crashes trying change settings on notes (including one just clicking "Visible"), but not reproducibly.

QtCreator / gdb is no help in tracking this down; the crashes seem to occur in assembly code or other places where there is really nothing to look at.

Comments

• Jan 5, 2014 - 16:51
Status (old) needs info ⇒ active

Given that the crashes appear deep in assembly code, it doesn't surprise me it might be system-specific. Perhaps state-specific as well (meaning, depending on what else you've done since starting MuseScore). And the exact steps differ for me from case to case - sometimes it crashes *immediately* upon pressing the Beam button, sometimes it crashes only when I then click in the score, sometimes only if I try to make an adjustment in the Inspector after clicking Beam.

But here are exact steps that always reproduce this for me:

1) start MuseScore, load Promenade if not already loaded on startup
2) click the head of the C in the first meassure
3) press F8 to open Inspector if necessary
4) press Beam button

This crashes immediately for me. Hopefully someone else on Windows 7 can verify?

Unfortunately, as I said, the stack trace is useful. 20 levels deep, it's still all assembly. The only semi-useful bit of information is that at level 18, the name of the function shows as ZN20QDeferredDeleteEventD0Ev in Qt5Core.dll. Above that, the function and file names all show processing to be within system DLL's (eg, C:\Windows\system32\ntdll.dll). But also, a whole lot of "??" entries:

0 ntdll!TpWaitForAlpcCompletion C:\Windows\system32\ntdll.dll 0x77800575
1 ?? 0x28d0a8
2 ntdll!AlpcMaxAllowedMessageLength C:\Windows\system32\ntdll.dll 0x777ba6ec
3 ?? 0x26ac83c0
4 ntdll!RtlReleasePebLock C:\Windows\system32\ntdll.dll 0x777635b7
5 ?? 0x7f
6 ?? 0x5d4
7 ?? 0x28d170
8 ntdll!LdrLoadAlternateResourceModuleEx C:\Windows\system32\ntdll.dll 0x777634a2
9 ?? 0x26ac8398
10 ntdll!RtlValidateHeap C:\Windows\system32\ntdll.dll 0x7780172e
11 ?? 0x18700000
12 ntdll!AlpcMaxAllowedMessageLength C:\Windows\system32\ntdll.dll 0x777bac29
13 ?? 0x18700000
14 ntdll!LdrLoadAlternateResourceModuleEx C:\Windows\system32\ntdll.dll 0x777634a2
15 ?? 0x26ac8398
16 msvcrt!free C:\Windows\syswow64\msvcrt.dll 0x752498cd
17 ?? 0x18700000
18 ZN20QDeferredDeleteEventD0Ev C:\Users\Marc\Src\MuseScore\win32install\bin\Qt5Core.dll 0x689ef3d3
19 ?? 0x26ac83a0
20 ?? 0x19e82970

Reply

• Jan 5, 2014 - 17:17

Still not reproducable here. Maybe someone with Windows 7 or other system can reproduce it. It is odd that the stach trace does not contain any musescore specific functions. Do you collect the stach trace from within QtCreator?

Reply

• Jan 5, 2014 - 18:22

Yes, that's from QtCreator. If others are unable to reproduce on Windows but wish more more complete backtrace or dump info, let me know how you'd like it.

Reply

• Jan 6, 2014 - 20:58

FWIW, no crash here. Running Fedora 19, x86_64 and Ms 30e0623.
I notice Qt was updated yesterday, don't know if that's relevant.

Reply