Crashing in 4.4.4 Arch Linux

[sheeb1]

Issue type

Crash or freeze

Description with steps to reproduce

1. Open musescore
2. Create new score
3. Start writing (recreation of what i was writing attached)
4. It crashes
   bug.pdf

Supporting files, videos and screenshots

^While writing, crashed ~15 seconds later

What is the latest version of MuseScore Studio where this issue is present?

4.4.4

Regression

Yes, this used to work in a previous version of MuseScore 4.x

Operating system

Arch Linux

Additional context

No response

Checklist

• This report follows the guidelines for reporting bugs and issues
• I have verified that this issue has not been logged before, by searching the issue tracker for similar issues
• I have attached all requested files and information to this report
• I have attempted to identify the root problem as concisely as possible, and have used minimal reproducible examples where possible

[MarcSabatella]

It's impossible to say from just a picture how you went about adding that music. Please ZIP and attach the score at the state just before the step that causes the crash, then give the precise instructions to recreate the crash from there.

It kind of sounds like you are saying the crash happens not in response to a specific action. In which case it could be the autosave kicking in and the crash happens there. Again, try saving your score explicitly.

Also, be sure to be using the official supported build of MuseScore Studio - the AppImage you download directly from musescore.org or GitHub. Unofficial / unsupported third party builds often have issues that lead to crashes and other problems that don't happen with the trusted builds.

[sheeb1]

testscore.zip
I'm using the arch linux package for musescore which says its upstream URL is musescore.org, would this also be official?
https://archlinux.org/packages/extra/x86_64/musescore/

[Jojo-Schmitz]

No, on the AppImage from https://musescore.org/en/download/musescore-x86_64.AppImage or those from GitHub are official and supported here

[seascallion]

I am seeing this issue too, on v4.4.4 on Arch Linux. (Upgraded via pacman - currently the latest official version in the Arch package registry.) Here's how I repro it on that test file:

1. Select the quarter note in Contrabasses measure 5
2. Set it to an eighth note (shortcut: 4)
3. Set it back to a quarter note (shortcut: 5)

This consistently causes a failure with these logs:

14:47:38.670 | INFO  | main_thread     | ActionsDispatcher::dispatch | try call action: pad-note-4
/usr/include/c++/14.2.1/bits/stl_vector.h:1237: std::vector<_Tp, _Alloc>::reference std::vector<_Tp, _Alloc>::back() [with _Tp = mu::engraving::MeasureBase*; _Alloc = std::allocator<mu::engraving::MeasureBase*>; reference = mu::engraving::MeasureBase*&]: Assertion '!this->empty()' failed.
zsh: IOT instruction (core dumped)  mscore -d test.mscz

The crash seems to be happening most often when overwriting eighth rests.

[seascallion]

Ok, I tried the same on the official download build (AppImage), and it didn't crash. I'm curious what the build process that creates the official Arch version, and how it's different from that one. Normally my workflow involves using pacman and yay to install and upgrade all packages, but might need to maintain this program separately for this reason.

[MarcSabatella]

Presumably they have turned on debug mode or otherwise enabled assertion failures. That is but one of very many things third parties tend to get wrong when trying to build MuseScore. So even if they managed to fix this particular problem, it’s still not going to be a good idea to use anything but the official build, which is also trivially simple to update (run from command with “update” option).