crash when selecting measure with a local time signature
P1 - High
S1 - Blocker
After writing some scores with about 20 staves,
I am experiencing fatal crushes on a score with a 140kb size.
As soon as I clic or paste it crushes: program closes. Already sent many time details via built-in bug reporting system.
IS there any solution/patch or am I doing something wrong? Is the file too big? (say a 30 page score?)
Is there any limitation?
Problem occurred after I ran an antivirus (MacKeeper). Is there any issue about this?
I am working with this, if it is a "go-pro" issue no problem, program is really worth it. But I couldn't find any useful explanation up to now...HELP
GIT commit: 6347ed6
Could you attach here your score?
use the "File attachments" option at the bottom of the page, just above the Save and Preview buttons when you're typing your post.
Better to use the forum: https: //musescore.org/en/forum/6
5-Scena e Duetto.mscz
So you are apparently using 184.108.40.206 on a Mac, ammebding Version info of this issue accordingly
And no, you never provided any details via the built-in bug reporting before.
It certainly is not a 'go-pro' issue, as there is no pro version of MuseScore, just a pro account on MuseScore.com.
We indeed need more Information, the score giving you that crash would be a good starting point.
Next a step-by-step procedurte to reproduce the crash (a simple click anywhere or a random copy/paste doesn't crash for me, MuseScore 2.0.3 on Windows 7).
The file certainly is not too big.
probably the built-in bug-report system is just an Apple thing? If there is any specific, let me know.
This is the score, tried to post it, trying again.
5-Scena e Duetto.mscz
check this (220.127.116.11 not 3.0, it seems to me)
If you don't mean the MuseScore menu entry Help → Report a Bug, then yes, this seems Apple specific and unrelated to MuseScore
(for the benefit of others, see also https://musescore.org/en/node/150671)
Shoichi change that score to use page view. If you can reproduce the issue with continuous view (how exactly?) but not with page view, this would mean 2 things: 1st you have a good workaround and 2nd we have a detail more for the investigation ;-)
I confirm it is 2.0.3, and that I reported from within tha app only now,
I tried to save in page view, then clicked on a note (it sounded) then tried to move around tiwh arrows, after a couple of moves, crushes. Re-opened, a single clic on an empty bar, crush. ... I have no clue
When I open it, even a single clic on an empty bar (towards the end, like you want to input more music) it cruches.
If I copy couple of bars and paste on an empty bar, crushes.
If it is not the file, what could be?
Using othe previous files, same staves, program works...
I still can't reproduce
Ah, now I can! Click on any staff into measure 287, where then 13/8 time sig starts
That measure Shows an invisubel 13/8 time sig, a right-click &rarr: measure properties though shows a nominal duration of 78/104 and an actual duration of 78/4, which doesn't really go tother at all
The latest development build crashes immediatly on opening that file with the following message:
Fatal: Mscore: ticks_beat(): bad divisor 104 (...\MuseScore\libmscore\sig.cpp:26, int Ms::ticks_beat(int))
The question now is: how did you get into this trouble?
I reverted to factory setting, opened the file, same crash.
The invisible 13/8 bar is a special bar only for 2 staves, to input a cadenza while other staves have a regular 6/8 and a fermata.
To me, it shows 13/8 regularly when I edit it. Had other similar bars, they are not an issue. Program allows to input different tempos.
Feeling is: I ran the antivirus MacKeeper while program was open, may have cleared /canceld some invisible files, cache, or other items?
I have/had no virus, it just ran ...
Oh, a local time sig it is. I believe there are know issues with those
Trying to change that bar's tempo,
I try to change it into a 2/2, wheel starts spinning, still spinning....there's an issue right there...
in fact program is stuck doesn't respond
not tempo but time sig I assume
to fix the file select measure 286, shift+click measure 288, Ctrl+Del to delete them (Cmd+Del on a Mac), then insert 3 new measures and enter the musik again
Or just drag a 6/8 timesig into all 3 measures, then delete them again, then check whether any notes got lost
I feel dummy now, could have canceled before, knowing that there was an issue with time sig.
Now look fully working.
Thank a LOT LOT LOT
Maybe related to #42341: Local time signature change results in corruption or #51271: Issues adding local time sig to score with parts
Both 5-Scena e Duetto.mscz and 5-Scena e DuettoBis.mscz crash MuseScore when I try to open them and print
libmscore/sig.cpp:Ms::ticks_beat: Mscore: ticks_beat(): bad divisor 104just before the crash.
OS: Debian GNU/Linux 9 (stretch), Arch.: x86_64, MuseScore version (64-bit): 3.0.0, revision: b3feb3a
Doesn't crash in current master anymore
Automatically closed -- issue fixed for 2 weeks with no activity.