Win3WMServer did not signal event about win3wm HOT 5 CLOSED

So I'm not really sure what caused this, but my suspicion is that the x86 server didn't die, and it was already occupying the pipe.
so the next time you started the program it silently died and couldn't resolve the connection since the named pipe was occupied.

to resolve this issue, if you see the problem happening, go to task manager and then to details, check if x86ipc.exe is a process and if it is then kill it, and try start win3wm again.

from win3wm.

So I'm not really sure what caused this, but my suspicion is that the x86 server didn't die, and it was already occupying the pipe.
so the next time you started the program it silently died and couldn't resolve the connection since the named pipe was occupied.

to resolve this issue, if you see the problem happening, go to task manager and then to details, check if x86ipc.exe is a process and if it is then kill it, and try start win3wm again.

Thank you for your help. I cannot find the x86ipc.exe in the task manager, but the problem was resolved today automatically. I guess I just need to restart my pc to fix the issue. However, I am doing some work and not be able to restart the pc, I will verify it later today.

from win3wm.

I have tested and confirmed that the problem can be resolve by restarting the pc. I also noticed that it only happen if exit the app using the taskbar icon, it works alright if exit the app using the hotkey.

from win3wm.

hmm thanks for the info, I'll try to reproduce the problem today and patch it

from win3wm.

I haven't been able to reproduce this issue even exiting the program with the taskbar icon

from win3wm.