musescore / musescore/MuseScore

High CPU consumption and overheating when network access is blocked by a local firewall

Open
#34,169 2 comments 0 reactions 2 assignees View on GitHub

@RomanPudashkin is already working on this.

Since Jul 15, 2026.

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

Description

Issue type

Other type of issue

Description with steps to reproduce

The high CPU consumption can be triggered when using the macOS open-source firewall LuLu (https://github.com/objective-see/lulu) to manage network permissions. Testing under different network conditions yields the following results:

Wi-Fi Connected + Network access BLOCKED via LuLu: CPU usage spikes significantly, and the Mac starts overheating.

Wi-Fi Connected + Network access ALLOWED via LuLu: The application runs normally with standard CPU usage and no heating.

Wi-Fi Disconnected: The application runs normally (as MuseScore makes no attempt to request network access).

Supporting files, videos and screenshots
Image Image
In which versions of MuseScore Studio is this issue present?

4.7.4

Regression

I was unable to check

Operating system

macOS 26.5.1

Additional context

Hypothesis

It appears that when MuseScore attempts to access the network but is continuously blocked by a local firewall, some internal network retry logic might fall into an infinite loop or poll too aggressively, ultimately leading to the high CPU consumption.

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.