Holodeck continues running after process closes about holodeck

[kolbytn]

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.

[daniekpo]

@kolbytn I haven't been able to repro this bug

[jaydenmilne]

Have you been using the repo he linked?

[daniekpo]

Yeah! I ran it a few times and checked top but couldn't find any holodeck process

[kolbytn]

That's odd because it was happening consistently to me. And you're using Ubuntu? Make sure to run main.py long enough for all the environments to load up. You can use --viewport so that the environments will display.

[daniekpo]

Oh! Maybe that's why. I was running it from a remote session. I'll have to set up a Linux environment on my local machine coz my network isn't fast enough for any display forwarding/remote desktop method that I've tried

[kolbytn]

I saw the issue ssh'd into a lab machine as well. You shouldn't need to run locally. Just make sure you let it run for long enough to see Holodeck appear on htop in the first place.

[daniekpo]

Ok. I think I accidentally left it running for about an hour and killed main.py, but I still could not see traces of Holodeck. How long did you have it running?

[daniekpo]

@kolbytn, I was finally able to reproduce it. I was sending it SIGINT by doing ctrl-c, but I think what you were talking about was killing/exiting the terminal which sent SIGHUB. Either way, I installed signal handlers for those events.

[kolbytn]

Awesome thanks! I thought I was doing ctrl-c over ssh, but I may be mistaken. Hopefully that problem is gone for good.

[daniekpo]

Resolved in #419