Score now crashes randomly and crashes every time I try to generate pdf parts and score

• Feb 16, 2023 - 22:36
Reported version
4.0
Type
Functional
Frequency
Once
Severity
S2 - Critical
Reproducibility
Always
Status
needs info
Regression
No
Workaround
No
Project

Previous save was working fine. Now my score with changes made today crashes randomly and also crashes at every attempt to generate a PDF Score and individual parts.

021523 - 01 Works

021623 - 01 Crashes
021623 - 02 Crashes

In going back through and trying to generate parts one at a time, Vibe 4 causes the crash. I deleted it and so far am able to generate parts. However...
all corrected pedal markings and graphic dynamics ( > style decrescendo ) are missing agin.

021623 - 02 - SCORE NO VIBE 4

@Marc Sabatella
This is the same score that I had to go back and redo all pedal markings and dynamics. Now I will have to do this yet again. With no exaggeration, this will make about the tenth time I've had to correct pedal markings, graphic dynamics and diminuendo markings.

There is obviously a problem with either Vibraphone instrumentation, pedal marking, dynamics, etc. some where.

Again, I realize you guys are volunteers but this is infuriating and time consuming to have to do the same corrections over and over.


Comments

I re-saved as a new name. There were also parts for instruments I didn't add (an additional Chime and 2 Crotale parts). I deleted them. Added another Vibe part. Then an additional Crotales part that I did not add just showed up again.

It is also now mis-numbering measures in the score. There are 2 m46's. I can't get it to change even when I change to numbering only the beginning measure of each system.

Do you have precise steps to reproduce the problem? We'd love to help, but it's pretty much impossible to do anything without precise steps to reproduce the problem. Once you have those and we can confirm the problem, then you can open an issue on GitHub so the developers can begin working on a fix.

In reply to by Marc Sabatella

The steps were pretty simple. All I did was add a vibraphone part (Vibraphone 4). I changed the name to Vibraphone 4 in all the pertinent places. I either copied and pasted notes from other parts (from Marimba 2, or input them individually. When I went to generate parts and print to PDF and the program crashed. I tried the same with parts after reopening. Crashed again. Went back to a previous save. Add the instrument again, same steps. Same problem.

I even went so far as to delete the Vibraphone 4 part, generate parts to print to PDF and it worked fine.

A good portion of problems that I am having all centered around the Vibraphone (other pieces as well).

It's still not clear to me if you have precise steps. to reproduce a specific problem. I see many different scores attached here, and lots of references to various things to try, no but no specific precise list of steps to follow. Please, attach one single score, and list the precise steps to reproduce the problem - numbered for clarity like this:

1) open the attached score
2) click this
3) click that
4) click this other thing

Result: crash

Once there is a precise set of steps to follow, then someone can attempt to confirm the problem.

Latest development builds reports the score to be corrupt:
Corrupted measure: Full score, measure 42, staff 4.
Corrupted measure: Full score, measure 42, staff 5.
Corrupted measure: Full score, measure 42, staff 9.
Corrupted measure: Full score, measure 43, staff 4.
Corrupted measure: Full score, measure 43, staff 5.
Corrupted measure: Full score, measure 43, staff 9.
Corrupted measure: Full score, measure 47, staff 12.
Corrupted measure: Full score, measure 47, staff 13.
Corrupted measure: Part score: Vibraphone 2, measure 42, staff 1.
Corrupted measure: Part score: Vibraphone 2, measure 43, staff 1.
Incomplete measure: Part score: Voice, measure 47, staff 1. Found: 0/1. Expected: 7/4.
Corrupted measure: Part score: Vibraphone 1, measure 42, staff 1.
Corrupted measure: Part score: Vibraphone 1, measure 43, staff 1.
Corrupted measure: Part score: Marimba 2, measure 42, staff 1.
Corrupted measure: Part score: Marimba 2, measure 43, staff 1.
Corrupted measure: Part score: Marimba 3, measure 47, staff 2.
Corrupted measure: Part score: Timpani, measure 47, staff 1.

See How to fix MuseScore 4 corrupted files

Punta_Patri Musescore 4 - 021723 - 01 - SCORE NO VIBE 4 - MEASURE FIX.mscz

But the others probably suffer from the same corruptions. Get yourself a nightly builds (from master) and open these scores with it

Indeed, that particular score is corrupt, which will of course lead to crashes. I don't get a crash in either 4.0.1 or current builds of 4.0.2 using either of the steps of steps listed, but no doubt, crashes can happen on corrupt scores. So now the question now, how to reproduce the corruption in the first place.

Nightly builds are created every day incorporating the latest bug fixes and other changes and made available for testing. Right now there are two parallel sets available - ones that will eventually become 4.0.2 and include only the fixes targeted for that release, and ones for the "master" branch including all changes, including ones that may not appear in a release until later. You can download and test these builds via the Download menu above, just scroll down until you see the Development builds section.

Anyhow, the score above is corrupted, so as mentioned, it is not really surprising bad things will happen when working on it. The real task is to identify the steps that lead to the corruption.

The extra crotales parts is probably from the same sort of corruption as was seen in #343121: Changes to one specific part not saving. Which could be a clue to the steps - it's probably something you did in both scores that is unusual enough than no other MuseScore user has performed those same steps (or else there would other reports of this).

As per my previous reply: "You can download and test these builds via the Download menu above, just scroll down until you see the Development builds section".