-
Notifications
You must be signed in to change notification settings - Fork 25
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 import job? #31
Comments
I just don't see anything in the code that could leak. There's no caching, no collections, tasks are all joined. Maybe one of the chain clients has a leak. Probably need to use a heap profiler. Other jobs use low memory. |
I know people have used massif for heap profiling rust. |
Import job was taking 50% of ram when I logged in. |
Memory usage looks much better after some dependency upgrades. |
Memory usage for the import job was at a steady low number, but today I noticed that Arbitrum fell behind, and memory usage is at 27%. Is there some memory being held by import jobs that run forever? I don't know what it would be. |
Memory usage immediately rises to 20% again. |
There's probably a memory leak in the import job. Recently the entire machine came down after the import process was killed, and just now I see it is using 30% of the machine's memory. It should be using just a low constant amount of memory.
The text was updated successfully, but these errors were encountered: