[Bug] MuseScore 4 process does not end properly when closing

[ThePython10110]

Issue type

Other type of issue

Bug description

When closing MuseScore 4, for some reason, the process is still there. Currently, I don't have MuseScore open, but all the processes from the previous times I've launched it are still there (since I last rebooted). They aren't really doing much, but still. A bigger issue is the fact that when attempting to end the task, it doesn't work. When doing it through Task Manager, it just silently fails, but when doing it through Process Explorer, it says "Error terminating process: Access is denied."

Steps to reproduce

Open MuseScore 4 Close MuseScore 4 Check Task Manager or another app with similar functionality

Screenshots/Screen recordings

No response

MuseScore Version

4.2.1

Regression

Yes, this used to work in MuseScore 3.x and now is broken

Operating system

Windows 10 Version 2009, Arch.: x86_64

Additional context

No response

[dcorson-ticino-com]

Curious, it is working properly for me.

OS: Windows 10 Version 2009 or later, Arch.: x86_64, MuseScore version (64-bit): 4.2.1-240230937, revision: github-musescore-musescore-d757433

[MarcSabatella]

Do you perhaps have VST instruments or effects loaded? How about if you reboot? How about if you do Help / Revert to factory settings (after first making sure there are no other running processes)?

Since this isn't something that happens normally and probably others won't be able to reproduce the issue without more info, it is probably best to ask for help on the support forum at musescore.org to try to isolate what specific attribute of your system configuration is triggering this.

[Sergio-Acevedo]

Happens on Arch Linux as well. I just use the package from the official Arch Extra repository. I don't tinker with any back-end related settings or custom effects/instruments; I just edit/playback files with the stock content of the program. Restarting Musescore, then closing it again will not kill the process, it has to be forcibly killed, rebooting the OS fixes it as well of course.

OS: Arch Linux, Arch.: x86_64, MuseScore version (64-bit): 4.2.1-, revision: github-musescore-musescore-

Musescore package source: https://archlinux.org/packages/extra/x86_64/musescore/

Here you can see that there is no Musescore icon on my taskbar because I "closed it", yet there is still that highlighted mscore process as shown by btop, still using 825MB of memory.

...

I don't know how relevant this may or may not be to the problem at hand, this could possibly be its own ticket, but sometimes when closing a file, the program seems to try to gracefully shut down instead of just returning to the "Scores" home screen to open a new file as shown by: 00:50:24.702 | INFO | main_thread | App::run | activeThreadCount: 0 00:50:24.783 | INFO | 136500905768640 | {anonymous}::alsaThread | exit 00:50:24.849 | INFO | main_thread | main | Goodbye!! code: 0 I haven't checked to see if this only happens when the problem process is there or not, but so far I haven't replicated this without its presence. I'll note that this process doesn't always persist when closing mscore, I haven't deduced yet what behaviour it may be that causes this to occur.

[Jojo-Schmitz]

For Arch Linux: check whether the AppImage has the same issue, if not, complain to Arch Linux, as their builds are not supported here

[Jojo-Schmitz]

2 more users with that problem in https://musescore.org/en/node/347774

[yamisama]

Same here on Windows 10, MuseScore 4.3.2. This also prevents installation of updates via MuseHub since the application is running. For me, too, the process cannot be killed using Windows Task Manager, the command just seems to have no effect.

[ThePython10110]

For Arch Linux: check whether the AppImage has the same issue, if not, complain to Arch Linux, as their builds are not supported here

For me, everything seems to work fine on Arch (the AppImage and extra/musescore package). Maybe they fixed this, or maybe it was just an issue on @Sergio-Acevedo's system.