If you are here from a search at an awkward hour, the answer is below the fold and the commands are copy-pasteable.
The problem
Restarting makes it go away, which is exactly why it comes back on a schedule nobody has written down.
What actually finds it
Point KiokuGraph at the dump from the crash and it returns the dominator tree, the objects ranked by what they actually retain, and the line of your code responsible.
Read the full article
Details and the runbook: https://kiokugraph.io/blog/outofmemoryerror-complete-guide/
Anyone else been bitten by this in production?
Top comments (0)