Skip to content

Heavy Memory Leak #738

Closed
taoteh1221 opened this Issue May 28, 2016 · 8 comments

5 participants

@taoteh1221

Node type: geth
OS: linux ubuntu
Network type: main
Mist version: 0.7.4

See screenshot. This is on a 4GB RAM system. System froze right after I barely got this screenshot. Highest wallet thread RAM usage hit 2.6GB max before system froze. Mist wallet memory usage increased slowly over 3GB RAM used until system was not responsive.
snapshot1

@hautdoge
hautdoge commented May 29, 2016 edited

Node type: geth
OS: Windows 10 x64
Network type: main
Mist version: 0.7.4
I have the same issue.. When I try to watch the DAO contract and try to look at my balance/do some voting, the Wallet completely freezes, and I can see it eating up 10GB+ of my RAM

@m0se
m0se commented May 30, 2016

I can confirm this as well, strange enough that I didn't experience this with the same Mist/geth version on my old slow 4GB Debian MBA,.. but now on my new machine with 16GB one of the "Ethereum-Wallet" processe eats all my memory.

I as well watch Maker/theDAO token and contracts.

Node type: geth 1.4.4-stable-94ad694a
OS:Linux 4.5.0-2-amd64 / Debian stretch
Network type: main
Mist version: 0.7.4

@luclu
ethereum member
luclu commented May 30, 2016

Thank you for reporting!
I will close this issue as it is a duplicate of #726.
Please feel free to append any new/missed out information over there.

@luclu luclu closed this May 30, 2016
@larspensjo

This report (memory leak in Mist) is not the same as #726 (memory leak in geth).

I added theDAO as a watch contract, Mist got unresponsive, and is currently using 17GB of RAM.

@luclu
ethereum member
luclu commented Jun 1, 2016

@taoteh1221 This is caused by an unoptimized event-handler which bombardes geth with requests. Both issues are the same although the title of #726 is misleading.

@taoteh1221

@luclu I agree with you, it was @larspensjo who said it was different, not me. When I created this issue I only saw geth in the subject line on that other issue, so I though it was separate.

@luclu
ethereum member
luclu commented Jun 1, 2016

@taoteh1221 my fault! sorry for that ;=)

@taoteh1221

@luclu No problem, thanks for all your hard work! :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.