Score corrupted then crashed
Reported version
3.x-dev
Type
Functional
Frequency
Once
Severity
S2 - Critical
Reproducibility
Always
Status
active
Regression
No
Workaround
No
Project
I'm working in 3.5 RC, on Windows 10. Worked on the score on Saturday, saved, closed as normal. This morning, I open the file, and it says it corrupted in bars 1323 (added a half rest in stave 1) and 1478 (in stave 1, completely empty). I clicked 'Ignore', and went and fixed the problem in 1323. (I copied the other staves in that measure, then ctrl+del the extra rest, changed the bar length in bar properties, then pasted the other staves in place.) Then I went to 1478, and it crashed.
| Attachment | Size |
|---|---|
| Cox_and_Box_Full.mscz | 2.77 MB |
Comments
Try the attachment again. Better use the forum https://musescore.org/en/forum/6
In reply to Try the attachment again… by Shoichi
Thanks, Shoichi. Could you clarify for me what the difference is between a bug report and an issue report? I've never been quite sure where to post my problems. :)
Oh, no, Shiochi--I just noticed...one of the parts is missing. The Piano/Vocal part is not there. And before noticing, I saved your version over my original version. gulp What do I do? (I don't want to just create a new part because I've spent hours working on layout, changing the height of every single vertical frame, adjusting the spacing of measures, system and page breaks, etc...!?)
Oh gosh, and I just noticed all my hours and hours of work on the other parts is also gone. I've literally spent an entire week doing layout on each part. 8-10 hours/day for a week or more, dealing with vertical frames and such. And all that's gone now. What do I do? How can I revert it?
Okay--I managed to restore a backup from Saturday morning...but it's still missing almost all the work I did on it on Saturday.
Download your first attachment
phew okay, never mind. I realised I was able to open the score I attached here, and then I just fixed the corrupted bars myself. So I have my original file again, but fixed. Still, hopefully, if whatever caused the corruption can be discovered and sorted out to prevent it from happening in the future, that'd be nice. :)