Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The dialog for closing an unsaved score is slow #26988

Open
4 tasks done
GrantCRodammmer opened this issue Mar 8, 2025 · 0 comments
Open
4 tasks done

The dialog for closing an unsaved score is slow #26988

GrantCRodammmer opened this issue Mar 8, 2025 · 0 comments
Assignees
Labels
P2 Priority: Medium performance Performance issues (e.g. high CPU usage) regression nightly Works correctly in the latest released version and is broken in the nightly builds UX/interaction

Comments

@GrantCRodammmer
Copy link

GrantCRodammmer commented Mar 8, 2025

Issue type

UX/Interaction bug (incorrect behaviour)

Description with steps to reproduce

  1. Create a score
  2. Close it
    Takes about a second for the dialog to appear.

Supporting files, videos and screenshots

Screen.Recording.2025-03-08.at.10.44.53.AM.mov

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

4.5 Nightly

Regression

Yes, this works in the latest released version and is broken in the nightly builds

Operating system

macOS 15.3.1

Additional context

This is on an M4 MacBook Pro, so it should be very fast.

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
@muse-bot muse-bot added regression nightly Works correctly in the latest released version and is broken in the nightly builds UX/interaction labels Mar 8, 2025
@cbjeukendrup cbjeukendrup added the performance Performance issues (e.g. high CPU usage) label Mar 9, 2025
@bkunda bkunda added the P2 Priority: Medium label Mar 11, 2025
@bkunda bkunda moved this to To do in MuseScore Studio 4.6 Mar 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P2 Priority: Medium performance Performance issues (e.g. high CPU usage) regression nightly Works correctly in the latest released version and is broken in the nightly builds UX/interaction
Projects
Status: To do
Development

No branches or pull requests

5 participants