Holodeck continues running after process closes
See original GitHub issueDescribe the bug The holodeck backend continues running after the process terminates. Not sure in what cases this happens, but it probably has something to do with threading.
To Reproduce
Run holodeck using the repo found at https://github.com/kolbytn/holodeck-baselines
. Then quit the process. Holodeck should still be running.
Expected behavior The holodeck backend should exit when the frontend exits.
Version Information:
- Ubuntu
- Holodeck Version 0.3.1
Issue Analytics
- State:
- Created 3 years ago
- Comments:11 (11 by maintainers)
Top Results From Across the Web
The Holodeck and the Inception Problem : r/DaystromInstitute
Their cell is an active holosuite that closes behind them and doesn't respond to vocal commands. Kirk, only passingly familiar with holodeck ......
Read more >Star Trek: Every Holodeck Accident In The Franchise (So Far)
Holodeck malfunctions are an often-used plot device in the Star Trek franchise and have provided various series with some of their best ...
Read more >Emergence (episode) - Memory Alpha - Fandom
A series of puzzling events on and off the holodeck lead the crew of the Enterprise to a surprising conclusion: The ship is...
Read more >Holodeck Malfunction - TV Tropes
The heroes inside the sim may be able to fight their way out, or make the sim release them after a certain procedure...
Read more >python - Keep secondary process running after main one closes
You can simply use os.fork() : from os import fork child_pid = fork() if child_pid == 0: '''This is the child process, i.e...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
That should have been enough time. I was only running for maybe 2-5 minutes each time, but I ran it repeatedly… You could try running it for a few minutes, killing the process, and then spinning up a new one. Do that several times and see if you can see anything. I’ll try again myself when I can.
Resolved in #419