Release 1.1.8 and 1.2.0beta7 (updated with 1.2.0beta8): possible memory leak (or not) #9550
scarletbright
started this conversation in
General
Replies: 2 comments 2 replies
-
Some new numbers from the stable (1.1.8) version: after being up for 1d22h16min29s, the amount to "leaked" memory is 16Gb!
|
Beta Was this translation helpful? Give feedback.
0 replies
-
Graphs from beta8 look quite different
|
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello everyone!
In attempt to trace regular sigterms, I've attached heaptrack to my mina nodes.
I would like to share the results here, hopefully they can be useful. I'm not sure the reported memory leak is actually an issue, so yes... just sharing my observations.
So, yesterday my stable (1.1.8) node core dumped after being up for 9h 42mins
systemd log:
apport log:
heaptrack logs:
Complete mina export-logs (218.2 Mb)
Complete heaptrack logs (242.9 Mb)
I also have a core dump file, but it's 3.7Gb
After the restart the node has worked for three more hours and then:
heaptrack log this time:
Complete heaptrack log (88.6 Mb)
Now the node is up for 12+ hours.
System info:
Ubuntu 18.04.6 LTS
8c/16t i9-11900K @ 3.50GHz
32Gb RAM
mina 1.1.8 running BP + snark worker
And what about 1.2.0beta7?
Well, it's currently up for almost 20 hours. Currently heaptrack is saying:
last five exit codes:
System info of the server running beta:
Ubuntu 18.04.6 LTS
12c/24t AMD Ryzen 9 3900X @3.8GHz
64Gb RAM
mina 1.2.0beta7 running BP only (no snark worker)
Again, I'm not even sure if those leaked numbers indicate or problem or not. Just sharing for what it's worth 😃
I don't think I was able to find the reason of sigterms, but well.... 😄
✌️
Beta Was this translation helpful? Give feedback.
All reactions