musescore / musescore/MuseScore
High CPU usage even when idle (25%)
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 15.1k
- Forks
- 3.3k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 91
Description
Description:
MuseScore 4.4.4 on Porteus 5.01 uses about 25% CPU when idle, even without any interaction or playback. This is much higher than MuseScore 3.6.2, which uses around 0-1% CPU when idle.
Steps to Reproduce:
- Start MuseScore 4.
- Create a new score (choose "Symphonic Orchestra").
- Wait for the audio samples to load.
- Minimize the window to ensure there is no keyboard or mouse interaction.
- Run
topor another system monitor to observe CPU usage.
Expected Behavior:
MuseScore should use little to no CPU when idle.
Actual Behavior:
MuseScore uses approximately 25% CPU even when idle, which seems unnecessary and leads to battery drain.
System Information:
- OS: Porteus 5.01 (64-bit)
- CPU: Intel® Core™ i5-4200M CPU @ 2.50GHz
- RAM: 7.7 GiB
- GPU: Intel® HD Graphics 4600
- MuseScore Version: 4.4.4 (AppImage)
Additional Information:
This issue is specific to MuseScore 4, and MuseScore 3.6.2 does not exhibit this behavior on the same system.
Supporting files, videos and screenshots
What is the latest version of MuseScore Studio where this issue is present?
MuseScore-Studio-4.4.4.243461245-x86_64
Regression
Yes, this used to work in MuseScore 3.x and now is broken
Operating system
Porteus Linux 5.01 64 bits xfce
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
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.