musescore / musescore/MuseScore
Lagging when working with large scores
Open
Nobody has claimed this yet.
needs review
performance
- Dominant language
- C++
- Stars
- 15.1k
- Forks
- 3.3k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 91
Description
If you are working with a large score for around 15 minutes. Musescore starts lagging and starts claiming it doesn't react. Especially when you have saved the file
Steps to reproduce the behavior:
- Open any large score (for instance a large string orchestra with a lot of woodwinds, brass, and percussion)
- Work on it for 5-10 minutes on the score
- Save the score
- Continue working on the score
- Eventually (with different timing) it will start to claim it's not working and starts to lag on every command you put in.
Expected behavior
Simply that it doesn't become slower the longer you work (very basic, I know)
Platform information
- Asus TUF gaming laptop running Windows 11
Additional context
A possible flaw is that I opened old musescore files. Saved on musescore 3.6.2 and opened them with musescore 4 (beta)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.