There can be cases where sometimes the Java process isn't getting terminated correctly/completely (which can also cause this issue). Hopefully I fixed at least the more obvious culprits of that in the latest update, but if it's still happening to anyone in 0.50+, just let me know :)