-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Memory leak in agent when re-running failed tasks #333
Comments
I'm a bit confused here, is this still happening post-undefined fix on the tasks? |
It happened post fix because I had changed the rediscovery timeout to 1 second (to replicate the issue) and that queued up over a thousand failed tasks. Whenever my agent started, it consumed memory at a visibly apparent rate until it hit around 8 GiB, when it was terminated by node. I don't believe I have seen this issue since, so this can be closed. It might be reopened if someone else is also getting this bug on their systems (given they are on the latest version) |
That's not a good sign. You should think about why it happened. |
By checking my logs, I can see that the memory leak does still occur and it does crash my agent occasionally. As such, I'm reopening this issue and attaching a snippet of my |
Describe the bug
When rediscovery tasks failed, they got added to a re-attempt list. This kept happening, and the tasks kept getting added to the re-attempt list, until the agent ran out of memory and crashed. When it restarted, it kept doing the same.
Running it on staging (1.14.0) fixed this issue and there were no more memory leaks. After analysing the journalctl, this was the finding.
Crash stacktrace:
The memory usage spikes to around 9 gigs, then the process crashes.
To Reproduce
It wasn't possible to reproduce the bug. However, it happened consistently. (see additional context)
Expected behavior
The memory leak shouldn't happen
Screenshots
Platform
Additional context
Notify maintainers
@aryanjassal @tegefaulkes
The text was updated successfully, but these errors were encountered: