musescore / musescore/MuseScore

Problems with parts; crashed 3 times, no dmp first, dump second and third.

Open
#16,250 3 comments 0 reactions 1 assignee View on GitHub

@cbjeukendrup is already working on this.

Since Aug 17, 2023.

crash P1 parts
Dominant language
C++
Stars
15.1k
Forks
3.3k
Avg merge
2d 2h
Merged PRs (30d)
91

Description

Describe the bug
Problem with parts - I've been testing MU 4.0 by entering this score. So far I cannot isolate the exact cause of the crash. However, without the parts, MU was not crashing.

I don't know if the crash could be reproduced even if I could reproduce the exact steps. I include a zip with:

  1. the log file,
  2. the other standard inclusions, and
  3. the latest save of the score.
    ShinyStockings-crash-2.zip

To Reproduce
This is a general description of what I did between finishing the score (just needed a small number of staff-measures entered) and the crash.

  1. After finishing the score, I created the parts.
  2. I set the zoom on the drumset part to 75% and dragged it to the Home position.
  3. I adjusted the drumset part to make the "hint" staff only shown when containing notes.
  4. I loaded a saved style file. I forced the style to be applied to all parts.
  5. I set the zoom on the Alto 1 part to 75% and dragged it to the Home position.
  6. Fixed voice 2 parts that should not be visible to not be visible.
  7. I adjusted the size including stretching the 11 measure rest at the top. In adjusting, I removed then replaced a "keep together in same system" element because the element is not local to the part.
  8. I set the zoom, etc. for Alto 2 part.
  9. Fixed voice 2 parts that should not be visible to not be visible.
  10. I adjusted the Alto 2 part.
  11. I set the zoom, etc. for Tenor 1 and Tenor 2 parts (but did not fix the not-visible part or adjust the sizes).
  12. I saved.
  13. I tried to close the score.

Expected behavior
MU doesn't crash.
(Also: see additional context)

Screenshots
NA

Platform information

  • Windows 11
  • 230370506-4.0.2-aabbec1-x86_64

Additional context

  • The problem with not visible parts not copying correctly has been reported elsewhere.
  • The problem with parts not having an initial zoom (zoom=0%), has been reported elsewhere.
  • The problem with the initial position of the parts has been reported elsewhere.
  • The problem with multi-measure rests not being formatted correctly has been reported elsewhere.
    The above are all problems which might have contributed to the crash. I had created parts earlier while entering the score, but I deleted them because I was having too many problems, including crashes. Working without the parts, MU was relatively stable though measures with non-visible elements did not work well and glissandi have problems reported in another issue.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.