-
Notifications
You must be signed in to change notification settings - Fork 20.4k
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
Geth nodes crashes, memory leak #3002
Comments
I can confirm seeing the same issue with geth version 1.4.11-stable-fed692f6 on Debian. The problematic block is block #2283416. Possibly the payload in this transaction: https://etherchain.org/tx/0x5c19695f50a30abbadfeef201d695d9c95c254534019e2f6a7a590e9ef246e82 |
yikes |
|
Be careful what you read on the internet everyone. Not everyone posting comments here is a |
Please wait for official security alert to be published at https://blog.ethereum.org/ - until then be careful what people claim. So far we can confirm a memory leak in go-ethereum master branch (and probably earlier releases). More info soon. |
Here are some GDB crash logs :
|
I confirm the problem with geth 1.4.11 |
Seems to be the same on develop branch HEAD too. |
@devktor It seems to be an invalid msg at EDIT : Im wrong here. Plz ignore. Its at @devktor can you give us max verbosity logs? |
I think you are on to something here. |
@sandakersmann we can confirm this by seeing if geth 1.4.9 cashes as it was before the HF and does not have this. Do you ahve a synced chain to test this? |
@colm, 1.4.9 would not sync the ETH chain. It would sync the ETC chain where the transaction in question does not exist. |
@trapp haha yeah my mistake. |
here are full logs with GDB:
|
@devktor Do you have a lot of |
@colm yes, I have bunch of them. |
@colm here are some geth logs right before crash:
here are GDB logs:
|
Not sure if related, but the block that triggers this issue has another transaction with an unusually high gas limit and gas usage: https://etherchain.org/tx/0x7bf56f8f9b98e51fd7d1c76818f6c0607e9738f191afae87edd3a34595803455 which calls the contract at 0xd6a64D7E8C8A94fa5068ca33229D88436A743B14 (without passing any data). |
We have identified the issue, working on a fix. |
@fjl care to elaborate? |
Does it have to do with the HF code @fjl ? |
@ChuckSRQ no, the attack is not network level (speaking only as someone completely unofficial who's overheard some discussions, read a bit of code, and independently decompiled some contracts; take it with a grain of salt). If it had to do with the hard fork code you'd also expect all implementations to be equally vulnerable. Geth only and memory overflow points to a flaw in memory management in Go. |
@pdaian Right. Only Geth seems to be affected. I guess what I'm really asking is does it affect Geth in ETC as well? Is it possible that it has only to do with the code added on to Geth for the DAO Fork? |
@ChuckSRQ Geth in ETC is definitely affected if my understanding is correct. Whether or not anyone is actively running the attack (aka whether the attack has replay protection or not), I have no idea. ETC developers watch this space ;). |
This looks like the fix here. |
Fixed and released as Geth 1.4.12. Thank you everyone for your support in tracing this issue. |
how can I upgrade ethereum on Ubuntu ? apt-get shows that there is no upate |
System information
Geth version: 1.4.10-stable-5f55d95a
OS & Version: Arch
Expected behaviour
Actual behaviour
Geth nodes crashes after a few minutes.
Steps to reproduce the behaviour
Start geth node, try to sync
Log:
http://pastebin.com/kVjhA2vU
I guess the problem is the VM codehash da002555
The text was updated successfully, but these errors were encountered: