Consistent Crash when Deleting Measure

• Feb 23, 2025 - 21:12

Hello Musescore Community,

I have a project file that is consistently crashing on my system. Here is what I'm using:


OS: Universalblue (use audio applications in an Arch container from distrobox)
Kernel: Linux fedora 6.12.15-200.fc41.x86_64 #1 SMP PREEMPT_DYNAMIC Tue Feb 18 15:24:05 UTC 2025 x86_64 GNU/Linux
Pipewire
Musescore 4.4.4-2 (using from Arch Linux in distrobox but the crash also occurs in the same version flatpak)

Basically, if I try to delete measure 59 in this musescore file in the treble clef, it immediately crashes musescore. This is a problem, since I'm currently on a tight deadline for notating and writing this harp piece. Any help would be appreciated!

I tried rolling back to a previous version of musescore to see if I could continue, but previous versions won't open newer files. I guess I'll just have to export music xml and continue in lilypond.

Here is what the output of the application says when launched from a shell:


/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; reference = mu::engraving::MeasureBase*&]: Assertion '!this->empty()' failed.
Aborted (core dumped)

Attachment Size
Imaginations: Mvt. 3.mscz 46.57 KB

Comments

• Feb 23, 2025 - 21:28

EDIT: I was able to get around the crash for now by exporting musicxml (with complete layout) and then importing it back into musescore as a new file. However, if I start to delete page and system breaks, then musescore will abruptly crash. May be a useful piece of information for squashing this bug.

Reply

• Feb 24, 2025 - 17:13

Looking at the mscx inside the mscz reveals:

<museScore version="4.40">
  <programVersion>4.4.4</programVersion>
  <programRevision></programRevision>
 

The empty programRevision tag is a tell-tale sign that you're not using the official AppImage from this site here, but some unsupported third party build (like FlatPak). These are known to have serious issues.
Another sign is the abort on a failing assertion, those should only happen in Debug builds.

Grab the AppImage and retry, come back if that crashes too...

In the (official!) version for Windows I can't reproduce a crash by deleting random measures from that score

Reply

Do you still have an unanswered question? Please log in first to post your question.