musescore / musescore/MuseScore
Disconnecting from M-Audio AIR 192|6 causes MuseScore to hang
@RomanPudashkin is already working on this.
Since Nov 16, 2023.
- Dominant language
- C++
- Stars
- 15.1k
- Forks
- 3.3k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 91
Description
Issue type
Crash or freeze
Bug description
Similar to this issue.
MuseScore seems to have issues regarding closing and crashing. I've found that in multiple circumstances, the program refuses to close and remains in Task Manager as a "Suspended" process. The first instance occurred while trying to update. I clicked the update button, was told to close, closed MuseScore, and then was told to close again. I found MuseScore listed in Background processes, Suspended. The second instance was a crash related to selecting a MIDI controller. I attempted to add my MIDI controller (Studiologic SL88 Grand but I believe this may happen with any controller) and the program froze. This may be related to FL Studio being open simultaneously. Regardless, I went to Task Manager and the program was marked as Suspended again. In both cases I clicked "End Task" a few times and nothing happened. Afterwards, I went to Resource Monitor and attempted to both resume the process and kill it. Resuming the process yielded no error, but didn't actually resume it. Killing it led to an "Access is denied" system error. The first time this occurred, I rebooted my PC to not waste time, assuming it was an uncommon error.
The second time, I tried a few other things. Besides seeing if Windows could kill the process by mashing the "X" button until it was recognized as unresponsive, I tried to kill the process using CMD/Powershell. The results are as follows:
PS C:\Users\OMG meee :3c> taskkill /im MuseScore4.exe /f
ERROR: The process "MuseScore4.exe" with PID 3844 could not be terminated.
Reason: There is no running instance of the task.
PS C:\Users\OMG meee :3c> wmic process where "name='MuseScore4.exe'" delete
Deleting instance \DESKTOP\ROOT\CIMV2:Win32_Process.Handle="3844"
ERROR:
Code = 0x80041003
Description = Access denied
Facility = WMI
I looked into a few other tools as well. ProcessExplorer gave the same "Access is denied" error. Process Hacker 2 gave a slightly different error:
Unable to terminate MuseScore4.exe (PID 3844): An attempt was made to access an exiting process.
After looking around on StackExchange, it seems that MuseScore has somehow become an unkillable process by some means. I don't really know what could be causing this, but I'm guessing it may be on the user end? I looked into the security permissions for the program and both my user and the system have full authority to terminate the process, as does another "NT AUTHORITY" "user." Even if the process has managed to make itself unkillable, I don't think I've personally done anything to cause this.
I haven't used MuseScore in a while and this only happened when returning to the program after several months. I don't believe this was an issue the previous time I used the program.
Steps to reproduce
1a. Open MuseScore
2a. Attempt to update in Muse Hub
3a. Close MuseScore
4a. Check Task Manager to see if process has been suspended in background
1b. Open MuseScore
2b. Cause crash (select MIDI controller in I/O preferences while FL Studio is open? I genuinely don't know what caused the crash, but it's sort of a minor issue to me at this moment)
3b. Check Task Manager to see if process is suspended in foreground and unkillable
Screenshots/Screen recordings
MuseScore Version
4.11? Whatever the latest update as of this morning is, but I can't check.
Regression
I don't know
Operating system
Windows 10 Home
Additional context
OS: Windows 10 Home 22H2 19045.3570
CPU: Intel Core i7-10700k
GPU: NVIDIA RTX 2070 Super
Memory: 32.0 GB
The only thing I noticed upon opening the program initially was it detecting a few Kilohearts VSTs I downloaded a couple weeks ago. Other than that, I haven't noticed anything out of the ordinary and even that doesn't really seem to present as an issue.
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.