3.5 Alpha
OS: Linux Mint 19.3, Arch.: x86_64, MuseScore version (64-bit): 3.5.0, revision: 1ee2fe3
Edit/Preferences->OK->Crash
:(
OS: Windows 10 (10.0), Arch.: x86_64, MuseScore version (64-bit): 3.5.0.11614, revision: 1ee2fe3
The same.
OS: Linux Mint 19.3, Arch.: x86_64, MuseScore version (64-bit): 3.5.0, revision: 1ee2fe3
Edit/Preferences->OK->Crash
:(
OS: Windows 10 (10.0), Arch.: x86_64, MuseScore version (64-bit): 3.5.0.11614, revision: 1ee2fe3
The same.
Do you still have an unanswered question? Please log in first to post your question.
Comments
Not for me
In reply to Not foe me by Jojo-Schmitz
Not for you, just for me...
Italian language, other machine
OS: Linux Mint 19.3, Arch.: x86_64, MuseScore version (64-bit): 3.5.0, revision: 1ee2fe3
From Windows I sent the report.
In reply to Not for you, just for me… by Shoichi
meetoo
UbuntuStudio 19.10.
In reply to Not for you, just for me… by Shoichi
Tried reverting to factory settings?
In reply to Tried reverting to factory… by Jojo-Schmitz
That fixed it. Thanks.
In reply to That fixed it. Thanks. by sammik
Not good though, means that 3.5 Alpha doesn't like some old setting. Would be helpful to find out which
In reply to Not good though, means that… by Jojo-Schmitz
Found some cases.
It is not only about old settings.
1) Setting "Start empty"
In this session ewerything works. But when you exit and start program again, You are in "crashing" mode, described above. (In dosent metter, if this option was set in old version, or after factory reset in 3.5.)
2) Something with locales. I cannot reproduce it, bu I have feeling, it is connected with locales settings (I had "system" language set and changed it to "english" in older version and may be som of this special combinations could make 3.5 goes into crash mode. but now, I cannot reproduce it anymore.
In reply to Not for you, just for me… by Shoichi
The info from Crash Reporter:
In reply to The info from Crash Reporter… by Anatoly-os
So at
I can confirm the crash over here as well (Win10 x86_64)
I took a copy of my preferences file before installing, so let's see if I can locate something that way.
In reply to I can confirm the crash over… by jeetee
OK, so the first thing that was very in my face is that the theme changed my MuseScore font (possibly a consequence of the new loading splash screen?)
Before:
theme\fontFamily=MS Shell Dlg 2
theme\fontSize=8
After:
theme\fontFamily=Segoe UI
theme\fontSize=9
Then there are a few new settings added to the file (so those are likely not the cause of the crash, as they're saved):
* in the [import] section:
compatibility\resetElementPositions=Ask
* in the [score] section:
harmony\play=false
andharmony\play\onedit=true
On a second run the crash can still be reproduced and the ini file is no longer changed (so likely crashing on the same point)
In reply to OK, so the first thing that… by jeetee
That theme change is due to a fix for the default fonts, #302114: Wrong default GUI font under Windows
might explain why it didn't crash for me: I had change that setting manually to the new one before
In reply to That theme change is die to… by Jojo-Schmitz
I don't think this crash has anything to do with that fix.
Concidentally, I experienced this exact same crash yesterday, and it happened while I was running inside a debugger. So I took a look.
The crash occurred inside the call from this line:
As far as I could tell, the crash was caused by the
svPanSettings
pointer containing a garbage value (notnullptr
).I restarted the app with a breakpoint set a few lines earlier so I could see try to see why it was happening, but I was never able to reproduce the crash again.
Just noticed that
SmoothPanSettings::loadFromPreferences()
isnullptr
-checkingmscore->currentScoreView()
, but the line settingsvPanSettings
in the first place is not:Very suspicious.
In reply to I don't think this crash has… by Spire42
Yup, crash is 100% reproducible when no score is loaded, because
mscore->currentScoreView();
returnsnullptr
. Adding anullptr
check around the three following lines fixes the crash.In reply to OK, so the first thing that… by jeetee
OK, what is very clear is that reset to default "fixes" this crash.
What is also clear is that reset to default simply erases a bunch of settings (perhaps entire groups) and that if you afterwards press OK in the preferences window many settings are now added into the preferences file as if you've changed them to a value which happens to be the default.
So far no clear culprit yet. Dayjob is asking some attention now, so I can't further pursue. Attached are my various versions of the ini-file in case someone else wishes to dive in.
Filed as issue #305106: Crash when applying preferences with no scores open with PR #6057.