musescore / musescore/MuseScore

Large scores are extremely slow to load

Open
#18,476 1 comment 1 reaction 2 assignees View on GitHub

Nobody has claimed this yet.

needs info performance
Dominant language
C++
Stars
15.1k
Forks
3.3k
Avg merge
2d 2h
Merged PRs (30d)
91

Description

Issue type

Crash or freeze

Bug description

They have loaded in a very large score of a full book of Beethoven's 9th symphony Op 125. Let's say a user needed to make a full score copy for their own band to play the music and you go on MuseScore.com to find a full score of it. But it is almost an hour long. So the user decides to download it so he/she can establish an arrangement for their own book of the master piece.

They opened up the score and it has started to lag unprecedently takes about 1 minute to open finally. Presses play on the menu works normal. After to start using the tools to edit the open score then the major crash/lag happens. Some times you need to force the program to get what you need. I can understand that this is a very large score and the program is very new. I don't know if this is a CPU issue on their end but it has become a noticed that something bad happens every time you load in a large score like these. The only way to close the program after the large lag is in the Task manager in the Windows menu. I am not sure what else to put in here but I think the video down below will help a lot!

Video report: https://www.youtube.com/watch?v=Kb9Xo9by1Y0

Steps to reproduce

1 Open musescore
2 load in the Beethoven score that is like 56 or longer
3 wait.... wait for a very long time
3 force close it with task manager

Screenshots/Screen recordings

https://www.youtube.com/watch?v=Kb9Xo9by1Y0

MuseScore Version

4.2

Regression

No.

Operating system

Windows 11

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.