MP 2.1 pre 2 on Windows 10. Client/server on one desktop box. MP exclusively used for TV, but desktop always has other applications running.
When the desktop is rebooted, I still (almost always) see the failure of the client to connect reported previously. (Red x, no guide, you found a race condition in startup of 2.1 pre, but that fix hasn't resolved this for me.) Some combination of restarting the server service & killing & restarting the client eventually gets them to connect. I don't have a recipe.
Probably related: When I close the client (BTW, it's usually a small window, not full screen), the window disappears as expected. But task manager shows the client running as a background process. If I try to re-open the client, nothing happens. If I kill the background client process(es), re-opening the client works as expected. I've taken to minimizing the client as a work-around, but it's still annoying. It seems to me that tearing down the window isn't causing the client to exit; attempting to activate the client sees the background (former client) process, so removes the duplicate - but a window isn't re-created. In any case, the background process shouldn't stay around consuming memory,
Log attached.
When the desktop is rebooted, I still (almost always) see the failure of the client to connect reported previously. (Red x, no guide, you found a race condition in startup of 2.1 pre, but that fix hasn't resolved this for me.) Some combination of restarting the server service & killing & restarting the client eventually gets them to connect. I don't have a recipe.
Probably related: When I close the client (BTW, it's usually a small window, not full screen), the window disappears as expected. But task manager shows the client running as a background process. If I try to re-open the client, nothing happens. If I kill the background client process(es), re-opening the client works as expected. I've taken to minimizing the client as a work-around, but it's still annoying. It seems to me that tearing down the window isn't causing the client to exit; attempting to activate the client sees the background (former client) process, so removes the duplicate - but a window isn't re-created. In any case, the background process shouldn't stay around consuming memory,
Log attached.