Hmm, I did it on WinXP pro SP3 and with an existing 1.2 score, but didn't think it might have been relevant?
Other than that I just dragged a random time sig from the palette onto a random measure and it crashed reliably.
It sometime didn't crash when I dragged onto the first measure, esp. if it was the same or a 'compatible' timesig (e.g. 4/4 vs. 2/2) as the one in place.
Does it still produce a crash with the newest nightly builds?
With the demo.mscx of #5 I am obtaining only a freeze due to an infinite loop because of the presence of tuplets.
I have ready a possible patch to cope with this infinite loop (it is just a minor correction), but I'd like to know if there is something more than simply an infinite loop.
Thanks.
I posted a pull request with a possible solution of the two bugs which were causing a freeze and a crash: https://github.com/musescore/MuseScore/pull/223
Please have a look at the comment to the pull request: with the first commit a deletion by Werner is being undone. I am not sure if this can re-introduce side-bugs because of which these lines were deleted.
A series of tests I have done with my personal build (under Windows XP Pro SP3) do not seem to bear to strange behaviors, but I think that there was a reason why those lines were deleted and I'd like to know it before accidentally messing up the code with my pull request.
Ciao,
ABL
Comments
I can't reproduce.
Can you give more details and the operating system?
Using MuseScore 2.0 Nightly Build (c64b066) - Mac 10.7.5.
Hmm, I did it on WinXP pro SP3 and with an existing 1.2 score, but didn't think it might have been relevant?
Other than that I just dragged a random time sig from the palette onto a random measure and it crashed reliably.
It sometime didn't crash when I dragged onto the first measure, esp. if it was the same or a 'compatible' timesig (e.g. 4/4 vs. 2/2) as the one in place.
Between your and my version https://github.com/musescore/MuseScore/pull/108 had been merged, and might have fixed the issue?
I'd have to wait for a new nightly build to verify
I can still reproduce in 37f118a
I can't reproduce with a new score.
Could you upload the score?
Using MuseScore 2.0 Nightly Build (37f118a) - Mac 10.8.2.
taken from the nightlybuild subdir if the current nighly build
Okay, I drag 3/4 onto the first bar and it crashes.
Using MuseScore 2.0 Nightly Build (37f118a) - Mac 10.8.2.
Does it still produce a crash with the newest nightly builds?
With the demo.mscx of #5 I am obtaining only a freeze due to an infinite loop because of the presence of tuplets.
I have ready a possible patch to cope with this infinite loop (it is just a minor correction), but I'd like to know if there is something more than simply an infinite loop.
Thanks.
Ciao,
ABL
I posted a pull request with a possible solution of the two bugs which were causing a freeze and a crash:
https://github.com/musescore/MuseScore/pull/223
Please have a look at the comment to the pull request: with the first commit a deletion by Werner is being undone. I am not sure if this can re-introduce side-bugs because of which these lines were deleted.
A series of tests I have done with my personal build (under Windows XP Pro SP3) do not seem to bear to strange behaviors, but I think that there was a reason why those lines were deleted and I'd like to know it before accidentally messing up the code with my pull request.
Ciao,
ABL
Changing status.
Should be solved in 90ba5f8.
Automatically closed -- issue fixed for 2 weeks with no activity.