MuseScore 3.7.0: Regression Crash: Dotted Quaver
Replication path
Press "." on the quaver shown in red in the last measure to make it a dotted quaver.
The software becomes unresponsive and then closes.
I have checked in Musescore 3.6.2 and it works without crashing.
Windows 10 64-bit
MuseScore 3.7.0.4133559636-x86
Comments
Is the 64bit 3.7 also showing the same crash?
In reply to Is the 64bit 3.7 also… by Jojo-Schmitz
I uninstalled it because plugins didn't work but I'll re-install it and check - but don't give it any priority as I have a workaround in 3.6.2.
Enjoy your weekend!
In reply to Is the 64bit 3.7 also… by Jojo-Schmitz
Same behaviour in 64-bit. The windows "busy" spinner for about 15 seconds and then MuseScore disappears. Task Manager confirms that MuseScore is no longer running.
In reply to Same behaviour in 64-bit… by yonah_ag
OK, confirmed. Firing up a debugger...
In reply to OK, confirmed. Firing up a… by Jojo-Schmitz
Stack trace (with a breakpont at musescore.cpp , line 3945):
1 Ms::mscoreMessageHandler musescore.cpp 3945 0x422e01
2 qt_message_print(QtMsgType, QMessageLogContext const&, QString const&) 0x68892408
3 qt_message(QtMsgType, QMessageLogContext const&, const char *, char *) 0x68892509
4 QMessageLogger::fatal(const char *, ...) const 0x68bfe272
5 qt_assert(const char *, const char *, int) 0x68bfde37
6 QVector::first qvector.h 242 0xffc2a9
7 Ms::Note::layout2 note.cpp 2111 0xa4493f
8 Ms::Chord::layoutTablature chord.cpp 2517 0x95031e
9 Ms::Chord::layout chord.cpp 1837 0x94c3db
10 Ms::layoutSegmentElements layout.cpp 99 0x9f2355
11 Ms::Score::layoutChords1 layout.cpp 156 0x9f251f
12 Ms::Score::getNextMeasure layout.cpp 3141 0xa01106
13 Ms::Score::collectSystem layout.cpp 4031 0xa06584
14 Ms::Score::doLayoutRange layout.cpp 5167 0xa0dc6f
15 Ms::Score::update cmd.cpp 302 0x536c88
16 Ms::Score::endCmd cmd.cpp 260 0x536926
17 Ms::Score::cmd cmd.cpp 4327 0x54ce55
18 Ms::ScoreView::cmd scoreview.cpp 2895 0x64b395
19 Ms::ScoreView::cmd scoreview.cpp 2089 0x642a17
20 Ms::MuseScore::cmd musescore.cpp 6621 0x434218
...
In reply to OK, confirmed. Firing up a… by Jojo-Schmitz
Culprit seems 43922443f33, reverting that fixes the crash
In reply to musescore-github-github… by Jojo-Schmitz
Fantastic! I'll look out for the next 'release'.
In reply to Fantastic! I'll look out for… by yonah_ag
Found potential fix, https://github.com/musescore/MuseScore/pull/14396
In reply to Found potential fix, https:/… by Jojo-Schmitz
Backported that to 3.7 now...
In reply to Same behaviour in 64-bit… by yonah_ag
4.0.1 doesn't crash on it either, so indeed a pure and plain 3.7 regression
In reply to Is the 64bit 3.7 also… by Jojo-Schmitz
where could I download Version 3.7?
In reply to where could I download… by wolfgan
See https://github.com/musescore/MuseScore/pull/9000
Thanks for the report! It should be fixed in the next build.
It's not the same subject but since this thread is about 3.7 I am posting here.
I can't access my pc now to see what build I am using. It's from appimage.
The descending arpeggio symbol has the arrow in the bottom but pointing upward. Was it a choice or a bug? It looks strange.
In reply to It's not the same subject… by fernandoamartin
Certainly a bug. More details please
In reply to Certainly a bug. More… by Jojo-Schmitz
OS: Ubuntu 22.10, Arch.: x86_64, MuseScore version (64-bit): 3.7.0.4165147589, revision: 8a17ff4
Appimage
The descending arpeggio symbol has the arrow on the bottom but pointing upward.
In reply to OS: Ubuntu 22.10, Arch.: x86… by fernandoamartin
Confirmed, and sounds familiar, IIRC for some reason SMuFL changed direction there, and MuseScore needs to adjust to that, seems that got done for master but not for 3.x
In reply to OS: Ubuntu 22.10, Arch.: x86… by fernandoamartin
See 25842144
In reply to OS: Ubuntu 22.10, Arch.: x86… by fernandoamartin
actually the culprit change was d200716 (which most probably got obsoleted by later changes), so I've reverted that now.
Thanks for the Report!
In reply to actually the culprit change… by Jojo-Schmitz
Someone or something seems to actively (?) cancel parts of the PR build, so no Linux version anymore/currently :-(
In reply to Someone or something seems… by Jojo-Schmitz
What does this mean?
In reply to What does this mean? by fernandoamartin
That for the time being there won't be any Linux AppImage artifacts from my PR #9000
In reply to That for the time being… by Jojo-Schmitz
Is it not better to take all the code, create a brandbnew repository and start a fresh project to avoid issues like that one?
In reply to Is it not better to take all… by fernandoamartin
Such a repository exists, it doesn't have all the GitHub CI bells and whistles though to automatically build stuff
In reply to Someone or something seems… by Jojo-Schmitz
Linux builds are back (for now) see also https://musescore.org/en/node/342126#comment-1176226
In reply to Linux builds are back (for… by Jojo-Schmitz
Great.
In reply to It's not the same subject… by fernandoamartin
It may be better to start new threads for new issues as it makes it easier to find them when browsing titles. If you start your thread with MuseScore 3.7.0: then this will also help with organisation.
In reply to It may be better to start… by yonah_ag
It would be nice to have an agreement.
In which forum session to post? Development? Other?
Will Jojo and other contributors check it always there?
In reply to It would be nice to have an… by fernandoamartin
I check every single post 😉
In reply to It would be nice to have an… by fernandoamartin
Development seems appropriate enough. I was just thinking that a new thread would be more visible to anyone else having the same issue, rather than it getting buried in an unrelated issue.