Closed cixastra closed 2 years ago
Thank you for your interest in Wisp!
I suspect that the memory leak is in your code rather than in Wisp library.
To verify this, can you try to run your code in a for
loop of maybe 100 iterations and see what is going on?
I'll try that! If the memory leak isn't in Wisp I'll look elsewhere! Thanks! (Don't close it yet, just in case it is wisp :))
I apologize! You were correct, the memory leak is in my own code. I'll have to look elsewhere. Thanks so much for this awesome scheduler!
You are welcome, I'm glad I could help!
Heyo! This scheduler is absolutely awesome first off! I am having an issue with the following code, the error is also below.
The code for the scheduler (whole file not included):
The scheduled code:
The container (this runs in a docker container for java) is not out of memory, but is actually only using 200/1024mb. Another issue is that with each execution, the memory usage gets higher, with no relief. But it levels out at 200mb, coincidentally when it stops working...