Process at port 8888 continues even after Tiled process has ended, on Windows

[rajasriramoju]

We saw an odd error when setting up Tiled on a windows machine. If a terminal running the tiled server was closed or if the process was ended manually, sometimes, upon starting a tiled process later, throws this error that port 8888 is already in use:

I had to manually look up the port information and is showed a 'LISTENING' status. The process needed to be manually killed before Tiled could be spun up again. And this was monitored when a Tiled process was terminated, and a new one was started again, eliminating the possibility of this being another process that was initialized between the end and start of the Tiled process. This could be a Windows specific issue, but we have to examine why this occurs for future setup.