Crash on some systems entering notes into a particular score

• Jan 19, 2021 - 20:08
Reported version
P0 - Critical
S2 - Critical

This only happens in the large orchestral score attached. I'm able to input notes in measures 1-119 with no issue, but when I try to input anything into measures 120-end, which are currently blank, the program crashes. This occurs using note inputs both from my computer keyboard and by clicking on the staff, and in all instruments.

Attachment Size
right pogging.mscz 393.73 KB


Regression No Yes
Priority P0 - Critical

Confirmed. And not related to continuous view (which those score is in. but crashes also in page view) and repeat barlines (there are none)

Status active needs info

I cannot reproduce in a current build. Is there a particular measure / staff / note I should be trying? I went with typing "A" a bunch of times starting in measure 119 and extended for several measures on the top staff, also trumpets, timpani, snare drum, and violins.

Title Musescore 3.6 Crashes With Note Inputs (Windows 10) Musescore 3.6 Crashes altogether !
Frequency Once Many
Severity S2 - Critical S1 - Blocker
Status needs info active

Musescore 3.6 Crashes altogether while starting ! I just updatet it, everything went fine until restart. Tried to download it again after uninstall. Nothing changed.

Title Musescore 3.6 Crashes altogether ! Musescore 3.6 Crashes With Note Inputs (Windows 10)
Frequency Many Once
Severity S1 - Blocker S2 - Critical
Status active needs info

Different issue surely (see
If it isn't (any of) that, share the score and the steps that lead to the crash.

Title Musescore 3.6 Crashes With Note Inputs (Windows 10) Crash on some systems entering notes into a particular score
Frequency Once Many
Severity S2 - Critical S1 - Blocker
Status needs info active

If you are seeing a crash just starting up, that's different, please reboot, uninstall, and reinstall, or try the "repair" option from the installer after the reboot. The reboot is important. If you continue to see a problem just starting, please ask for help in the Support forum.

Regarding the original problem, I can reproduce with the release version, but not with a current build. The fix involving start repeats doesn't seem like it could be relevant. But there are a couple of other possibilities. I'm looking into it further, I'd like to be sure understand why 3.6 crashes but my current build does not.

Building from the 3.6 sources I do get a crash though (strack in MSVC):
> MuseScore3.exe!Ms::Segment::element(int track) Zeile 426 C++
MuseScore3.exe!Ms::Measure::isCutawayClef(int staffIdx) Zeile 2910 C++
MuseScore3.exe!Ms::Measure::layoutStaffLines() Zeile 266 C++
MuseScore3.exe!Ms::Score::collectLinearSystem(Ms::LayoutContext & lc) Zeile 169 C++
MuseScore3.exe!Ms::Score::layoutLinear(bool layoutAll, Ms::LayoutContext & lc) Zeile 195 C++
MuseScore3.exe!Ms::Score::doLayoutRange(const Ms::Fraction & st, const Ms::Fraction & et) Zeile 4948 C++
MuseScore3.exe!Ms::Score::update(bool resetCmdState) Zeile 301 C++
MuseScore3.exe!Ms::Score::endCmd(bool rollback) Zeile 264 C++
MuseScore3.exe!Ms::Score::cmd(const QAction * a, Ms::EditData & ed) Zeile 4292 C++
MuseScore3.exe!Ms::ScoreView::cmd(const char * s) Zeile 2886 C++
MuseScore3.exe!Ms::ScoreView::cmd(const QAction * a) Zeile 2082 C++
MuseScore3.exe!Ms::MuseScore::cmd(QAction * a, const QString & cmd) Zeile 6631 C++
MuseScore3.exe!Ms::MuseScore::cmd(QAction * a) Zeile 6058 C++
[Externer Code]
MuseScore3.exe!Ms::ScoreTab::actionTriggered(QAction * _t1) Zeile 227 C++
[Externer Code]
MuseScore3.exe!Ms::runApplication(int & argc, char * * av) Zeile 7946 C++
MuseScore3.exe!main(int argc, char * * argv) Zeile 95 C++
[Externer Code]

in MinGW:
1 Ms::Segment::element segment.cpp 431 0xa6433f
2 Ms::Measure::isCutawayClef measure.cpp 2910 0xa0826f
3 Ms::Measure::layoutStaffLines measure.cpp 266 0x9f9e58
4 Ms::Score::collectLinearSystem layoutlinear.cpp 168 0xba59e8
5 Ms::Score::layoutLinear layoutlinear.cpp 192 0xba5bac
6 Ms::Score::doLayoutRange layout.cpp 4948 0x9e3902
7 Ms::Score::update cmd.cpp 302 0x53027e
8 Ms::Score::endCmd cmd.cpp 260 0x52ff1e
9 Ms::Score::cmd cmd.cpp 4292 0x545b45
10 Ms::ScoreView::cmd scoreview.cpp 2884 0x640416
11 Ms::ScoreView::cmd scoreview.cpp 2081 0x638357
12 Ms::MuseScore::cmd musescore.cpp 6626 0x432d4c
13 Ms::MuseScore::cmd musescore.cpp 6057 0x42f6cd
14 Ms::MuseScore::qt_static_metacall moc_musescore.cpp 523 0x5e4ca2
15 QMetaObject::activate(QObject *, int, int, void * *) 0x68a947f8
16 Ms::ScoreTab::actionTriggered moc_scoretab.cpp 225 0x603c00
17 Ms::ScoreTab::qt_static_metacall moc_scoretab.cpp 110 0x603688
18 QMetaObject::activate(QObject *, int, int, void * *) 0x68a947f8
19 QActionGroup::hovered(QAction *) 0x2cdd4db2
20 QActionGroup::qt_static_metacall(QObject *, QMetaObject::Call, int, void * *) 0x2cdd573c

Element* Segment::element(int track) const
    int elementsCount = static_cast<int>(_elist.size());   // elementCount contains quite a big number, 1892928134, regardless (or because?) _elist not being accessible. Maybe the optimizer is plaing dirty tricks here
    if (track < 0 || track >= elementsCount) {
        return nullptr;
    return _elist[track];    // crashes here, elist not accessible
Fix version