musescore / musescore/MuseScore

Panning Navigator is very slow

Open
#34,883 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

P3 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. With a big score open, open the Navigator
  2. Scroll sideways past the edge of the score visible in the Navigator.

Result: the framerate while scrolling instantly plummets. Panning back into the area already loaded into the Navigator is fast again.

Closing Navigator makes scrolling fast through the whole score.

Supporting files, videos and screenshots

https://github.com/user-attachments/assets/540e1cac-0b43-48ca-b61b-44587b6a3518

(Sorry, it's hard to demonstrate the issue well and stay under the upload file size limits.)

In which versions of MuseScore Studio is this issue present?

OS: macOS Sequoia (15.7.7), Arch.: arm64, MuseScore Studio version (64-bit): 4.7.5-260831071, revision: github-musescore-musescore-3654226

Regression

I was unable to check

Operating system

macOS

Additional context

No response

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.

Research direction

Start by reproducing the issue from the Navigator with a large score, scrolling sideways beyond the area already loaded. Trace the Navigator's panning and score-loading entry points while monitoring framerate on macOS. Done means scrolling remains responsive across the whole score with the Navigator open.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
desktop, performance
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.