Observations on the consistency of Musescore 3.6.x

• Jan 31, 2021 - 23:30

First let me make it clear that I appreciate the time and hard work that goes into each new release of Musescore. I have to admit, though, that 3.6 has been rather...inconsistent.

I just submitted another issue to the Tracker for another crash-inducing bug (re: opening the Timeline has a random chance to cause a crash). I figured the crash-inducing bugs were caught when 3.6.1 was released. But no. This one was present both in 3.6 and in 3.6.1. The crashes are honestly getting on my nerves. A stable release should not crash when trying to perform basic tasks. 3.6 crashed more than any other version in recent memory.

I can imagine how difficult it must be to catch every bug, and I do appreciate the effort you all have put into the upgrades in the latest releases. But I just don't get why crashes with such basic tasks as changing the order of instruments or opening the Timeline weren't caught before 3.6 was officially released. I may not be a developer, but as a user, it's rather frustrating as you can surely imagine.

Thanks for indulging my rant. Don't mean to be an armchair quarterback, so to speak. : ) Have a great day!


You mean #316756: 3.6.1 crashes at random on opening the Timeline? It just got reported so how could it have been fixed already? Also it is not reproducible...

Maybe you should have helped in testing 3.6 Alpha, Beta, RC. Admittendly 3.6.0 had pretty a bad bug, that is fixed in 3.6.1 though (see #315529: MuseScore 3.6 crashes on open of a file with start repeat in continuous view). And ever since at least 3.5 there's a problem where the updating itself can go wrong, we hope to have it fixed for 3.6.2 (see #275837: MuseScore crashes during start-up while displaying "Start center"), there the workaround that helped almost (?) always; reboot, reinstall and choose the repair option.

In reply to by Jojo-Schmitz

This post was a product of my impulsivity. You're right; those who don't aid in the testing can't exactly complain about the testing. Apologies. As for the Timeline issue, it's pretty rare. I'm not surprised it hasn't been reproduced yet. I had just updated after experiencing all the Ordering crashes back in 3.6, so when it crashed again I just reacted.

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