musescore / musescore/MuseScore

Slow when adding or inserting a new measure

Open
#24,632 12 comments 0 reactions 2 assignees View on GitHub

@RomanPudashkin is already working on this.

Since Sep 20, 2024.

needs review P1 performance regression MS3 UX/interaction
Dominant language
C++
Stars
15.1k
Forks
3.3k
Avg merge
2d 2h
Merged PRs (30d)
91

Description

Issue type

UX/Interaction bug (incorrect behaviour)

Description with steps to reproduce
  1. Create a score
  2. Add notes and everything you need to engrave
    i.e. Five part single staff per part (violin 1, violin 2, viola, alto voice, cello)
    Fill the score and than when you get to 25/30 measures the function add/insert measures starts to be very slow. Getting worst adding more elements to the score. With no notes or elements in the score everything is smooth and doesn't have any problem.
    P.S. Everything like adding notes and palettes is getting better with the new nightly, but the adding/inserting measures is still buggy and slow in the descripted cases.
Supporting files, videos and screenshots

issue.zip
issue

What is the latest version of MuseScore Studio where this issue is present?

Always has been there since 4.x and still there in the latest nightly 4.4.1.242481121 studio and hub

Regression

Yes, this used to work in MuseScore 3.x and now is broken
Adding measures feels slow in all versions of 4

Operating system

Windows 11

Additional context

This happens with two different machines surface pro 7 i5-1035G4 8gb windows 11
one desktop with AMD Ryzen 5 1600 Six-Core Processor 3.20 GHz RAM installata 16,0 GB windows 11

Checklist
  • This report follows the guidelines for reporting bugs and issues
  • I have verified that this issue has not been logged before, by searching the issue tracker for similar issues
  • I have attached all requested files and information to this report
  • I have attempted to identify the root problem as concisely as possible, and have used minimal reproducible examples where possible

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.