kokodev

9:01:26 AM [INIT] > 'Survival' has stopped successfully 9:01:28 AM [WARN] > 'Survival' is deadlocked, please kill it above to continue... well it does say has stopped successfully for some...

@macarooni-man The only way to resolve this is to force quit the host???

> [@kokofixcomputers](https://github.com/kokofixcomputers), I guess what I'm asking is this: > > 1. Does this happen in Vanilla over Telepath? NO > 2. Does this happen when running Fabric locally? YES

@macarooni-man I asked AI to see why killing is not working: 2. Process Name Matching Might Be Insufficient Your code checks for java.exe (Windows) or java (Linux/macOS) by name. However,...

> thanks [@kokofixcomputers](https://github.com/kokofixcomputers)! > > actually, auto-mcs has complete control over the Java wrapper, and it launches specifically from an internally managed Java environment. It's only an issue with Fabric,...

> [@kokofixcomputers](https://github.com/kokofixcomputers) can you send an .amb backup of your server? I'm unable to reproduce this on a stock Fabric server It takes a while. I think it happens after...

@macarooni-man Hey! So I made a bunch of other tests, and apparently, the kill button is already bugged. It won't kill Vanilla either. So maybe the issue with fabric not...

> [@kokofixcomputers](https://github.com/kokofixcomputers) can you provide any other information about the setup? What OS is this on, and more importantly, is it over Telepath? I tried both with and without telepath...

@macarooni-man And apparently, when using the kill button, java is killed successfully. But it didn't kill the console window host and others Some of these didn't exist before starting the...

> [@kokofixcomputers](https://github.com/kokofixcomputers) It's impossible to narrow this down without detailed information or a server backup. I'm unable to reproduce this issue, and it leads me to believe it might be...