Changing note to value exceeding bar causes crash chen lung • Mar 12, 2011 - 23:28 Type Functional Severity S2 - Critical Status closed Project MuseScore 1. Create 2/4 piano score. 2. Enter minim. 3. Select it and change to semibreve. Expected result: A minim appears in each bar with a tie between them. Actual result: Crash. Using MuseScore 1.0 and 2.0 nightly build (4079) - Mac 10.4.11. Reply Comments chen lung • Mar 12, 2011 - 23:29 Reply David Bolton • Mar 13, 2011 - 03:11 I can reproduce using the nightly build r. 4088, Windows 7, but MuseScore 1.0 does not crash for me. Reply chen lung • Apr 13, 2011 - 00:58 Status (old) active ⇒ fixed Appears to be fixed. Using MuseScore 2.0 nightly build (4172) - Mac 10.4.11. Reply David Bolton • Apr 26, 2011 - 05:12 Status (old) fixed ⇒ active Still crashes for me using the steps in the original report. (Tested using r. 4227 nightly build, Windows 7) Reply chen lung • May 1, 2011 - 10:31 Status (old) active ⇒ duplicate I realise this is a duplicate - reported already by Lasconic.#8057: [trunk] Changing duration beyond measure limit causes crash Reply System Message • Oct 31, 2018 - 09:00 Status (old) duplicate ⇒ closed Automatically closed -- issue fixed for 2 weeks with no activity. Reply System Message • Nov 1, 2018 - 09:00 Automatically closed -- issue fixed for 2 weeks with no activity. Reply System Message • Nov 2, 2018 - 09:00 Automatically closed -- issue fixed for 2 weeks with no activity. Reply System Message • Nov 3, 2018 - 09:00 Automatically closed -- issue fixed for 2 weeks with no activity. Reply System Message • Nov 4, 2018 - 09:00 Automatically closed -- issue fixed for 2 weeks with no activity. Reply System Message • Nov 5, 2018 - 09:00 Automatically closed -- issue fixed for 2 weeks with no activity. Reply System Message • Nov 6, 2018 - 09:00 Status fixed ⇒ closed Automatically closed -- issue fixed for 2 weeks with no activity. Reply
David Bolton • Mar 13, 2011 - 03:11 I can reproduce using the nightly build r. 4088, Windows 7, but MuseScore 1.0 does not crash for me. Reply
chen lung • Apr 13, 2011 - 00:58 Status (old) active ⇒ fixed Appears to be fixed. Using MuseScore 2.0 nightly build (4172) - Mac 10.4.11. Reply
David Bolton • Apr 26, 2011 - 05:12 Status (old) fixed ⇒ active Still crashes for me using the steps in the original report. (Tested using r. 4227 nightly build, Windows 7) Reply
chen lung • May 1, 2011 - 10:31 Status (old) active ⇒ duplicate I realise this is a duplicate - reported already by Lasconic.#8057: [trunk] Changing duration beyond measure limit causes crash Reply
System Message • Oct 31, 2018 - 09:00 Status (old) duplicate ⇒ closed Automatically closed -- issue fixed for 2 weeks with no activity. Reply
System Message • Nov 1, 2018 - 09:00 Automatically closed -- issue fixed for 2 weeks with no activity. Reply
System Message • Nov 2, 2018 - 09:00 Automatically closed -- issue fixed for 2 weeks with no activity. Reply
System Message • Nov 3, 2018 - 09:00 Automatically closed -- issue fixed for 2 weeks with no activity. Reply
System Message • Nov 4, 2018 - 09:00 Automatically closed -- issue fixed for 2 weeks with no activity. Reply
System Message • Nov 5, 2018 - 09:00 Automatically closed -- issue fixed for 2 weeks with no activity. Reply
System Message • Nov 6, 2018 - 09:00 Status fixed ⇒ closed Automatically closed -- issue fixed for 2 weeks with no activity. Reply
Comments
I can reproduce using the nightly build r. 4088, Windows 7, but MuseScore 1.0 does not crash for me.
Appears to be fixed.
Using MuseScore 2.0 nightly build (4172) - Mac 10.4.11.
Still crashes for me using the steps in the original report. (Tested using r. 4227 nightly build, Windows 7)
I realise this is a duplicate - reported already by Lasconic.
#8057: [trunk] Changing duration beyond measure limit causes crash
Automatically closed -- issue fixed for 2 weeks with no activity.
Automatically closed -- issue fixed for 2 weeks with no activity.
Automatically closed -- issue fixed for 2 weeks with no activity.
Automatically closed -- issue fixed for 2 weeks with no activity.
Automatically closed -- issue fixed for 2 weeks with no activity.
Automatically closed -- issue fixed for 2 weeks with no activity.
Automatically closed -- issue fixed for 2 weeks with no activity.