Closed sdizazzo closed 4 years ago
I have tracked down the memory leak to this loop: https://github.com/sdizazzo/pyaltitude/blob/09460875bd7cd45b472315876108048cf54b9191/pyaltitude.py#L127 which makes sense because thats where all the magic happens. I tried cleaning up the worker in the done callback among other things, but something more elaborate is needed or I missed something. At least for now I can slow it down by upping the timeout from 0.01
to 0.1
Resolved with https://github.com/sdizazzo/pyaltitude/commit/48c2cdc4a6cc466e5df491a534c458d9de2efb9d The queue was passed into the workers from when I was originally going to handle them as threads myself. So it never ended up blocking the main while loop so it was running out of control. Easy enough once I found it.