port already in use (due to slow shutdown of the debug build) [#21289]

[Edgar]

“Media server MediaMonkey Library could not start port 10827…”
In testing 3063 on my multi-monitor system I was repeatedly launching and closing MediaMonkey. I kept seeing this – more than 60% of the time. I was waiting at least a few seconds between closing and launching (I have an extremely fast computer) and it seems that if I waited about 5 seconds the odds were much better that this would not happen. Would it be possible to move releasing this port much earlier in the closedown routine?

[Lowlander]

That happens when MediaMonkey is still running. You should always wait for a program to fully close before relaunching when you're testing things.

[Edgar]

Agreed about waiting for an application to completely close, but…

I have been testing MediaMonkey 2024 quite extensively over the last few weeks; this testing has involved rapid closing and re-opening. Until version 3063 I have never seen this issue <shrug>.

[Lowlander]

It's been around forever. If you launch MediaMonkey prior to it being closed this has been an issue for a long time.

[MattTown]

It also happens when MM crashes or has to be closed from Task Manager. In those circumstances I have to restart the computer, even if I've terminated all of the MM processes I can find in Task Manager.

[Edgar]

Matt is correct.

[Lowlander]

Never seen that. However if I need to force close MediaMonkey I use the Details tab in Task Manager and use End process tree on MediaMonkey.exe, which will also kill the MediaMonkeyEngine.exe processes.

[rusty]

In my testing, this issue is specific to the debug build. Can you confirm that this is the case for you as well?

Thanks!

-Rusty

p.s. tracking this at https://www.ventismedia.com/mantis/view.php?id=21289

[rusty]

Based on the dev team's preliminary assessment, this is a limitation of the debug build and slow closing of MM debug will always occur if dbgview isn't running with the debug build to capture messages.

The solution for now would be to switch to the 'regular' build once testing is complete, but we plan to examine this further in the future.

Thanks!

-Rusty

[MattTown]

Never seen that. However if I need to force close MediaMonkey I use the Details tab in Task Manager and use End process tree on MediaMonkey.exe, which will also kill the MediaMonkeyEngine.exe processes.

Thanks Lowlander, didn't know that option existed. Will try that in future to see if it makes a difference - assuming of course that MM crashes in future after all the attention that the Devs are lavishing on it : )

Cheers
Matt

[rusty]

fyi, we've fixed the slow shutdown speed that occurred with the debug build so that this should no longer be an issue (except in the event of a crash in which MM fails to terminate properly). The new build should be available soon.

-Rusty