musescore / musescore/MuseScore
[MU4 Issue] [Muse Sounds] Musescore 4 crashes after selecting a specific bar (Linux)
@Eism is already working on this.
Since Dec 28, 2022.
- Dominant language
- C++
- Stars
- 15.1k
- Forks
- 3.3k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 91
Description
Describe the bug
When I select specific bar(s) or note(s) in score, it crashes MuseScore
I am using Linux Mint 20.3 Una
To Reproduce
Not sure how to reproduce on different devices.
When running through the terminal and selecting that bar it shows
`[51882:51882:20221227,121628.069986:ERROR file_io_posix.cc:144] open /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq: No such file or directory (2)
[51882:51882:20221227,121628.070012:ERROR file_io_posix.cc:144] open /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq: No such file or directory (2)
12:16:28.076 | INFO | main_thread | ActionsDispatcher | dispatch: try call action: note-a
/tmp/.mount_MuseScNoCR46/AppRun: line 26: 51874 Aborted (core dumped) "${APPDIR}/bin/mscore4portable" "$@"
Steps to reproduce from @DmitryArefiev
- Open Third_Date_.HTTYD3_String_Orchestra_Cover.copy.zip
- Enable MuseSounds (if not enabled)
- Go to Violins 2 staff, measure 89 and select F note
Expected behavior
It shouldn't have crashed
Screenshots
If applicable, add screenshots to help explain your problem.
Platform information
- OS: Linux Mint 20.3 Una
Additional context
This musescore file, when I used it a few months in 3.6.2 would come up with "This file is corrupted" errors and these specific bars would the ones that were corrupted. I fixed it by deleting the bar and recreating it.
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.