[Trunk] Crash when inserting a measure before the first one [DELETED] 5 • Jan 22, 2010 - 08:47 Type Functional Severity S2 - Critical Status closed Project MuseScore With nightly 2636, Create a new score in 4/4 Select 1st measure Press Inser or Create -> Measure -> Insert a measure --> Crash Reply Comments [DELETED] 3 • Jan 23, 2010 - 19:04 fixed in rev. 2639 Reply Thomas • Feb 6, 2010 - 19:05 Status (old) fixed ⇒ closed Automatically closed -- issue fixed for 2 weeks with no activity. Reply chen lung • May 6, 2011 - 08:43 Title Crash when inserting a measure before the first one ⇒ [Trunk] Crash when inserting a measure before the first one Status (old) closed ⇒ active Using MuseScore 2.0 nightly build (4233) - Mac 10.4.11. Reply schepers • May 31, 2011 - 03:01 Bug still reproduceable on the latest 4318 nightly build. You get a Microsoft Visual C++ runtime error crash. Reply schepers • May 31, 2011 - 03:25 See newer (duplicate) issue #10208: [trunk] Crash when inserting measure(s) on Measure 1 Reply chen lung • Nov 28, 2011 - 04:00 Status (old) active ⇒ duplicate 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
Thomas • Feb 6, 2010 - 19:05 Status (old) fixed ⇒ closed Automatically closed -- issue fixed for 2 weeks with no activity. Reply
chen lung • May 6, 2011 - 08:43 Title Crash when inserting a measure before the first one ⇒ [Trunk] Crash when inserting a measure before the first one Status (old) closed ⇒ active Using MuseScore 2.0 nightly build (4233) - Mac 10.4.11. Reply
schepers • May 31, 2011 - 03:01 Bug still reproduceable on the latest 4318 nightly build. You get a Microsoft Visual C++ runtime error crash. Reply
schepers • May 31, 2011 - 03:25 See newer (duplicate) issue #10208: [trunk] Crash when inserting measure(s) on Measure 1 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
fixed in rev. 2639
Automatically closed -- issue fixed for 2 weeks with no activity.
Using MuseScore 2.0 nightly build (4233) - Mac 10.4.11.
Bug still reproduceable on the latest 4318 nightly build. You get a Microsoft Visual C++ runtime error crash.
See newer (duplicate) issue #10208: [trunk] Crash when inserting measure(s) on Measure 1
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.