musescore / musescore/MuseScore

Crash Reporting processes fire regularly and consume the CPU

Open
#30,369 3 comments 0 reactions 1 assignee View on GitHub

@DmitryArefiev is already working on this.

Since Oct 14, 2025.

needs review P3
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

Ubuntu 22.04.5 LTS, Arch.: x86_64, MuseScore Studio version (64-bit): 4.5.2-251141401, revision: github-musescore-musescore-ac9d3bc

As a user, playing back mscz files,
whilst the application runs (without apparent failure from the user's persepctive),
crashpad_handle processes will be spawned and they consume the CPU for very long periods.

Can a configuration option be introduced to stop the Crash Reporting ?

Supporting files, videos and screenshots

Sample process:

PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
13512 user 20 0 895184 463044 6400 S 100.3 1.4 0:04.23 crashpad_handle

In which versions of MuseScore Studio is this issue present?

4.5.2-251141401

Regression

I was unable to check

Operating system

Ubuntu 22.04

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.