Closed Sirs0ri closed 8 months ago
Nice catch! Yeah that's a problem, i will release a fix later 🙂
Hey sorry for not responding in like a week.. i had a very important school assignment which is now over. I just fixed the issue, building now and should be out in roughly 10-15 minutes :slightly_smiling_face:
The Problem
When relaunching the app (either manually, or through the "relaunch" option in the system tray), the new session won't be able to connect to musicassistant, because the 1st instance's squeezelite background process never got killed.
This leads to a) the player not working at all, b) a warning being spammed in the MAss logs, c) visual glitches, because the display name of the companion player in the UI will be flickering between it's actual name and the player ID
This can be fixed by opening the task manager, finding the orphaned squeezelite process, and killing it manually.
Versions
Music Assistant Server: 2.0.0b73 Companion App: v0.0.20 Windows 10 22H2, build 19045.3516
Logs & Screenshots
MAss Log:
The active instance in Task Manager:![grafik](https://github.com/music-assistant/music-assistant-desktop/assets/6765536/365d095a-d845-4301-9c7e-fbe029360401)
The orphaned instance:![grafik](https://github.com/music-assistant/music-assistant-desktop/assets/6765536/bfb66b9d-bd5e-42b1-85e1-1d3755b203a3)