musescore / musescore/MuseScore

Crash when batch converting a mscz to a bunch of output files (the last of them is mp3 output)

Open
#26,237 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

cli community crash P2
Dominant language
C++
Stars
15.1k
Forks
3.3k
Avg merge
2d 2h
Merged PRs (30d)
91

Description

Issue type

Crash or freeze

Description with steps to reproduce
  • Unzip the following file: testscorefails.zip
  • Execute: MuseScore4.exe -j testscorefails.json

You get a "Segmentation fault" error.

I have attached the diagnostic file output in the following section

Supporting files, videos and screenshots
What is the latest version of MuseScore Studio where this issue is present?

OS: Windows 11 Version 2009 or later, Arch.: x86_64, MuseScore Studio version (64-bit): 4.4.4-243461245, revision: github-musescore-musescore-2232670

Regression

I was unable to check

Operating system

Windows 11

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

Reproduce the crash with MuseScore4.exe -j testscorefails.json after unpacking testscorefails.zip, and inspect diagnosticfiles.zip for clues. Trace the batch conversion path for the sequence ending in MP3 output; done means the supplied job completes without a segmentation fault.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.