Crash when closing score/application during Save Online

chen lung

• Nov 13, 2017 - 22:41

Reported version

2.1

Priority

P2 - Medium

Type

Functional

Severity

S1 - Blocker

Status

active

Regression

Workaround

Project

MuseScore

Open score.
'File'>'Save Online'.
'Save'.
Close score, or MuseScore before the dialogue appears.

Result: Crash (see attached log).

Note: The score does seem to upload successfully.

Using MuseScore 2.1, 2.2 Nightly Build 072c135 and 3.0 Nightly Build 528c131 - Mac 10.11.6.

Attachment	Size
Crash when closing score:application during Save Online [Log].txt	67.47 KB

Comments

Jojo-Schmitz

• Nov 14, 2017 - 02:52

Status (old)	active	⇒	needs info
Status	active	⇒	needs info

Which score? Or is it just any score? If so it got to be a new problem in musescore.com or relate to Mac and a special version of MacOS?

chen lung

• Nov 14, 2017 - 10:29

I managed with every score in trying to reproduce; no special version of Mac.

Jojo-Schmitz

• Nov 14, 2017 - 12:10

Works just fine for me, MuseScore 2.1, Windows 7

Jojo-Schmitz

• Nov 14, 2017 - 14:55

Looks like it is crashing at mscore/uploadscoredialog.cpp, line 150, I'm not sure though and woudn't know why

Jojo-Schmitz

• Jan 16, 2018 - 11:10

Status (old)	needs info	⇒	active
Status	needs info	⇒	active

chen lung

• May 11, 2018 - 18:09

Reported version

2.1

⇒

2.3

2.3-dev (3182aa5): I can't reproduce when quitting the application, but can if closing the score.

3.0-dev (396687c): I can't see Save Online.

OS: OS X 10.11.6
Arch.: x86_64

Jojo-Schmitz

• May 11, 2018 - 18:16

Severity	S3 - Major	⇒	S2 - Critical
Reported version	2.3	⇒	2.1

Try using -e to at least see the save online dialog

chen lung

• May 12, 2018 - 12:10

Thanks Jojo.

I managed to reproduce the score-closing crash (see attached log) in 396687c, but not the quit.

Does the 2.1 tag mean it applies to both 2.3 and 3.0 versions?

Attachment	Size
Crash when closing score during Save Online [3.0 Nightly].txt	74.97 KB

Jojo-Schmitz

• May 12, 2018 - 12:25

2.1 means it isn't a regression in 2.2 or 2.3
Whether Master AKA 3.0 is affected too needs to get checked, seems you just did that, right?

chen lung

• May 12, 2018 - 13:32

Thanks for explaining.

And yes, it affects both development versions (2.3 and 3.0) - the score-closing aspect anyway; perhaps there has been a change somewhere, since the initial report, in relation to the quit one.

Jojo-Schmitz

• May 30, 2018 - 09:25

Just stumbled across this again today. Reasone for the crash in the above mentioned place is of course that there is no currentScore() anymore, once all scores are closed.

Anatoly-os

• Nov 2, 2018 - 11:46

Severity	S2 - Critical	⇒	S1 - Blocker
Priority		⇒	P2 - Medium
Regression		⇒	No
Workaround		⇒	No

That is why we separated severity and priority. We can crash the software with "clicking too fast" scenarios but this is still not a priority :)