Closed CharliePoole closed 1 year ago
Turns out this only happens when there is an agent loaded using the TCP communication transport. Error is in engine, transferring this issue there.
Verified the problem still exists in the latest (dev-00024) build as well as in beta1 where it was initially detected.
This required a series of PRs but is now fixed in the 2.0.0-dev00032 build of the engine and the 2.0.0-dev00302 build of the GUI.
:tada: This issue has been resolved in version 2.0.0-beta2 :tada:
The release is available on:
Start the GUI. Click 'X' to exit. Check in Task Manager. The process is still running.
Using 'File | Exit' works correctly. 'X' should do the same thing.