Linux Crashes recently
I've been having challenges keeping Musescore running recently. I run Arch with a Wayland KDE on my desktop and qtile with X11 on my laptop. Both systems are experiencing relatively constant crashes in multiple scores (including new ones) and when doing several different activities. In other words, I'm not convinced it's a score/corruption issue and I've noticed it occurs after tasks as simple as selecting a note to as complex as adjusting page formats.
I have experienced this in the natively installed 4.4.4, the latest Flatpak, and in the latest officially supplied AppImage. The first version I noticed this on was 4.4.1 but it had been awhile since I used it before that so I don't know what version specifically these issues go back to.
As a specific reproducable example, I'm including a score that has arpeggios around measure 68. Just clicking on one of those arpeggio symbols causes musescore to crash.
Has anyone else been experiencing frequent crashes lately in a Linux environment?
| Attachment | Size |
|---|---|
| The First Noel (sax-piano).mscz | 40.33 KB |
Comments
Another example of this issue on the natively installed 4.4.4 on my desktop (Arch, Wayland, KDE) as well as 4.4.3 flatpak was creating a new score (using wizard), adding a single voice (the one named voice) instrument, setting 96 bpm, 21 measures and finishing the wizard. Then perform the following steps:
1. Click on second measure rest
2. Press "5" on the keyboard
3. Press "4" on the keyboard
4. Press "." on the keyboard
5. Press CTRL+z
6. Press CTRL+z
And it crashes at this point.
Another interesting feature is that when setting the bpm or the number of measures, Musescore will not take keyboard input. I have to click the arrows down/up to adjust. I think I've noticed this elsewhere but I can't recall where.
One nice thing about using the flatpak and launching it from terminal, is it seems to output information which may be relevant. Upon crashing using the above steps, the v4.4.3 flatpak outputs the following info:
10:28:16.219 | ERROR | 124383309846208 | SynthResolver::resolveSynth | invalid audio source params for trackId: 0
10:28:16.273 | INFO | 124383309846208 | FluidSynth::addSoundFonts | success load soundfont: /app/share/mscore-4.4/sound/MS Basic.sf3
10:28:16.275 | INFO | 124383309846208 | FluidSynth::addSoundFonts | success load soundfont: /app/share/mscore-4.4/sound/MS Basic.sf3
10:28:16.360 | ERROR | 124383309846208 | SynthResolver::resolveSynth | invalid audio source params for trackId: 1
10:28:16.365 | INFO | 124383309846208 | FluidSynth::addSoundFonts | success load soundfont: /app/share/mscore-4.4/sound/MS Basic.sf3
10:28:16.366 | INFO | 124383309846208 | FluidSynth::addSoundFonts | success load soundfont: /app/share/mscore-4.4/sound/MS Basic.sf3
10:28:22.426 | INFO | main_thread | ActionsDispatcher::dispatch | try call action: pad-note-4
10:28:23.302 | INFO | main_thread | ActionsDispatcher::dispatch | try call action: pad-note-8
10:28:24.436 | INFO | main_thread | ActionsDispatcher::dispatch | try call action: pad-dot
10:28:26.894 | INFO | main_thread | ActionsDispatcher::dispatch | try call action: undo
10:28:27.489 | INFO | main_thread | ActionsDispatcher::dispatch | try call action: undo
/usr/include/c++/14.2.0/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.
There are several other errors earlier in the flatpak load process so I'll attach a text file with the complete flatpak session messages.
I tested the crash scenario previously mentioned with the native and the flatpak versions in the appimage version. In this case, the appimage does not crash. However the feature where MuseScore does not accept keyboard input to set bpm and measure count is still present.