-
Notifications
You must be signed in to change notification settings - Fork 2.7k
Memory leak #3085
Comments
Note that apparently after running out of memory, validator nodes will get slashed as offline, so this is problematic for those running validator nodes. |
I have one node running without validator key and the memory is not increasing like in the validator node. |
what's the upper bound of this increase? the node just keeps allocating until it crashes or it stops at some point? If the latter, then maybe this is not actually an unexpected behavior. |
1.-what's the upper bound of this increase? 2.- the node just keeps allocating until it crashes or it stops at some point? |
Okay, I see. I don't suggest that it is a false alarm but it is also not super strange for a software which is not yet developed with optimization in mind to allocate (gradually) around 1Gb of memory. |
@iammelea could you try to replicate this with latest master and a small local chain? |
Can't reproduce it on a local chain. The memory grows a bit, but that's mostly database cache. |
I recently fixed some memory leak in Polkadot, maybe that solves your problem. But this was no "big" memory leak, so I'm not sure if it was the reason of your problem. |
@arkpar Thanks for the heads-up. libp2p/rust-libp2p#1217 should address that. |
v0.6.9 is out lets close this old issue |
Hello, validating in Poc-4 Alexander and we can see how the use of memory increases over time. here pic.
![Screenshot from 2019-06-20 14-31-33](https://user-images.githubusercontent.com/38863192/60278500-e0604a00-98ff-11e9-886a-b1578bf77614.png)
after stop and start the Polkadot process, the memory is back to a low level and starts increases over time again.
The text was updated successfully, but these errors were encountered: