ID:1552650
 
BYOND Version:506
Operating System:Windows 7 Home Basic
Web Browser:Chrome 34.0.1847.116
Applies to:Dream Seeker
Status: Open

Issue hasn't been assigned a status value.
Descriptive Problem Summary:
Closing out of a game client doesn't end the program.

Numbered Steps to Reproduce Problem:
Compile an environment (even new environment default).
Run the environment.
Close the client.
DreamSeeker is still running.

Code Snippet (if applicable) to Reproduce Problem:
N/A


Expected Results:
DreamSeeker process ends upon closing the client.

Actual Results:
DreamSeeker continues to run in the background.

Does the problem occur:
Every time? Or how often?
Every time.
In other games?
Multiple projects of mine, as well as default environment setup.
In other user accounts?
Yes.
On other computers?
Can't test personally.

When does the problem NOT occur?
When not using 506.1242.

Did the problem NOT occur in any earlier versions? If so, what was the last version that worked?
This bug is new to 506.1242. It didn't have the issue in 506.1240.

Workarounds:
For windows, use of the task manager to manually end the process.
I'm getting depressed over the multithreading failures. Might be time to put this out to pasture...
I had this problem through the entire 506 period, and I could never pin it down. It's not new in 1242.
I guess I just didn't notice it in the others. My bad.
In response to Tom
Tom wrote:
I'm getting depressed over the multithreading failures. Might be time to put this out to pasture...

Don't give up Tom! Everything new requires trial & error. We're trying to help you fix the problem, for we can have the perks of multithreading.
In response to Ter13
Ter13 wrote:
I had this problem through the entire 506 period, and I could never pin it down. It's not new in 1242.

Confirming the same thing. Mentioned it in the other bug report for Dream Daemon. Also tested back to the 504.1231 build.

If you're like me, and are compiling and running a lot, then you could create a batch that'll kill all dreamseeker/dreamdaemon instances without having to end task.

Just paste the following into a text file and save as 'kill byond.bat'

taskkill /f /im dreamseeker.exe
taskkill /f /im dreamdaemon.exe


Warning: This will kill any games you're playing too.
I especially ran into this when dealing with external DLLs; normally DS would close properly but if I made calls to an external DLL the DLL would keep DS loaded.
This seems to be caused by javascript running winget/winset commands right at close time.

this was in the arguments of one of the processes hanging around:

"C:\Program Files (x86)\BYOND\bin\dreamseeker.exe" "byond://winget?id=&property=url&callback=Byond.__callbacks__%5B2%5D"


whats actually going on is it's launching another ds process instead of handling the url and that one is just hanging around.
Can confirm this still happens.