Closed peterdsharpe closed 6 years ago
Wow, what an unexpected issue! If only I had documented this behavior in the readme!
The issue can probably be fixed if the child threads check for that the parent thread is alive and, if not, terminate the thread.
How's the motor test stand hardward going? Is it going to make it into the report? I really want some pitot tubes!
This is 100% a weird issue though. Not sure why the program is spawning separate subprocesses which aren't terminated on exit. I'll have to look into it.
I thought that was because of the weird multithreading thing you were trying to do originally; since we revised the entire app I don't think this should be an issue.
To Reproduce: Try to close the app System: Any