Crah after crash after crash
I do not understand what the f is going on. I had Musescore 3 on windows 10. Used it for few years. No problem besides a few crashes here and there. I updated to Musescore 4. Started crashing on startup or sometimes a little bit after creating new score. Uninstall, reinstall. Nothing. Reinstall MS3, also started to crash on start or little bit after creating new score, just like MS4.
Searched on web, nothing. For months the same shit. That system was Ryzen 5 with 16GB Ram. Now I get a new laptop. Windows 11, Ryzen 7 with 32 GB Ram. Install MS4, again crashing just a bit after creating a new score.
I have everything new on this laptop. Every driver up to date, every redistributable installed. This is not about opening a "corrupt file". I also have a Focusrite 2i2 4th Gen Audio Interface and latest drivers. I attach the latest crash log.
WTF is going on?
| Attachment | Size |
|---|---|
| MuseScore_241209_210635.txt | 19.69 KB |
Comments
In reply to This is not a crashlog… by mercuree
Yes I did but the crashing started after updating to version 4 and that was before getting the audio interface. I have not tried to use it recently without the focusrite. I will try but I do not think that will change anything.
Exact steps are: Open new score. Just Treble clef 4/4 piano nothing else. Wright couple of notes and creashes. Maybe even before I write the notes. As for Dorico, lol.
In reply to Yes I did but the crashing… by forpluginsnoname
Most Musescore users do not experience this problem. Your case is different.
What could be the differences? Differences in hardware, system settings, Musescore settings.
We do not know.
Your log file contains lines: MCursor::createScore | Not implemented!!
I looked at the Musescore code. It seems that such an entry appears when opening the "Create time signature" dialog box. Maybe you made some changes there that lead to a crash. Or maybe the crash is related to the changes in the palette that you made.
Musescore should not crash, of course, no matter what you did.
Try resetting Musescore to factory settings.
Did you drag a palette cell? Please provide the exact steps.
In reply to Did you drag a palette cell?… by krasko78
Like I said. Just create new score and crash.
For palettes, yes, I change place and move around the things to organize them. For example accidentals, because I mostly notate non western modal music. Is moving around different elements of the palettes a problem?
I'm having the exact same experience. Running Debian testing (but it happened on Debian 12, as well, so the version of the OS isn't a factor), and MuseScore Studio 4.4.3. I could be doing any of the following:
- adding lyrics
- adding or moving rests
- deleting notes
One time I pinned it down to a specific measure, deleted it, recreated it fresh, and the problem went away for that score. But there are other scores where I can't seem to identify the problem. tt seems completely random and is super frustrating!
I'm also running Gnome 47.2, and not KDE Plasma. I know this app on Linux is written with QT, but I couldn't say if I'm missing a library or have a corrupt one. Really could use a fix here. Thanks.