Large text size (max), caused crash - twice

• Dec 10, 2016 - 09:04
Reported version
2.1
Type
Functional
Severity
S3 - Major
Status
duplicate
Regression
No
Workaround
No
Project
MuseScore

Linux (Fedora 25, 64 bit). Musescore 2.03 rev 3c7a69d
Entered a small score. Set size to max. Printed OK.
Came back to app, unable to do anything. When I closed it, Fedora
reported the bug (said it was fed back).

Happened again 5 minutes later, still same max size. /layout/Page settings. Stave space set to 2.764mm.

Just now. Checked which setting. After seeing size, Quit app, discard changes. Fedora still reported a crash.

Comments

• Dec 10, 2016 - 14:58

In order to help we'd need you to attach the specific score and give orchids steroids to reproduce the problem. Fwiw, it's unlikely to be related to the size; 2.764 is nowhere near max.

Reply

• Dec 10, 2016 - 16:04

I cannot reproduce this behaviour using 2.0.1 on Win7. Score opens, plays, saves, and reopens with not problems of any sort.

(As for 'orchids steroids', I suspect that Marc meant to write 'precise steps' but the auto-correct on his device got carried away! ;o)

Reply

• Dec 10, 2016 - 16:21

Wow, major autocorrect fail indeed! :-) Anyhow, I can't reproduce either. Can you give "precise steps" to reproduce the issue, starting from:

1) start MuseScore
2) open score
3) ...

Reply

• Dec 10, 2016 - 16:25

Open MS
Automatically opens last score.
/layout/page settings
Scaling - select 2.964mm
Apply
OK
^p
Close window. Bombs.

Reply

• Dec 10, 2016 - 16:39

Sorry, even following those instructions (including opening the piano keyboard, which is what I got by typing UP+p), I still get no crash.

Reminder, I am on Win7, so perhaps this indicates an OS-dependent problem?

Reply

• Dec 10, 2016 - 16:49

^p = OS 'print' command?

I'm on LInux - could be a different issue altogether?

It tells me a "problem has been reported" though I can't find the log used.

Reply

• Dec 10, 2016 - 16:57

Still no crash. CTL+P is the equivalent Win7 OS print command; sent that and printed the score, then closed and reopened MuseScore. All is working as expected.

Reply

• Dec 10, 2016 - 17:22

One of our printers is an old, non-wifi laser that is hardwired to an XP desktop which isn't used very often anymore. When that desktop is off-line, that printer cannot be reached on the network. This has never created problems when running MuseScore in the Win7 machine.

Reply