Skip to content
This repository has been archived by the owner on Nov 6, 2020. It is now read-only.

Periodic snapshot maxing out RAM, interrupting sync #3027

Closed
rphmeier opened this issue Oct 31, 2016 · 7 comments
Closed

Periodic snapshot maxing out RAM, interrupting sync #3027

rphmeier opened this issue Oct 31, 2016 · 7 comments
Labels
F2-bug 🐞 The client fails to follow expected behavior. M4-core ⛓ Core client code / Rust.
Milestone

Comments

@rphmeier
Copy link
Contributor

reported by @mtbitcoin on gitter.

@rphmeier rphmeier added F2-bug 🐞 The client fails to follow expected behavior. M4-core ⛓ Core client code / Rust. labels Oct 31, 2016
@rphmeier
Copy link
Contributor Author

rphmeier commented Nov 1, 2016

(am unable to reproduce)

@gavofyork gavofyork added this to the 1.4 Civility milestone Nov 1, 2016
@gavofyork
Copy link
Contributor

gavofyork commented Nov 1, 2016

would be nice to have this cleared up with @mtbitcoin before releasing 1.4.0

@mtbitcoin
Copy link

mtbitcoin commented Nov 1, 2016

I've run this with --no-periodic-snapshot and the leak is still there. so this might not be related to the snapshots

@mtbitcoin
Copy link

could the memory leak be related to the --pruning=archive ?

@mtbitcoin
Copy link

The memory leak is looking more of an issue with the "--pruning=archive". I am testing this now ..

@mtbitcoin
Copy link

mtbitcoin commented Nov 2, 2016

Please close. Memory leak was due to running with --pruning=archive. Opened new issue at https://github.com/ethcore/parity/issues/3081

@tomusdrw
Copy link
Collaborator

tomusdrw commented Nov 2, 2016

Closing since new issue has been opened.

@tomusdrw tomusdrw closed this as completed Nov 2, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
F2-bug 🐞 The client fails to follow expected behavior. M4-core ⛓ Core client code / Rust.
Projects
None yet
Development

No branches or pull requests

4 participants