search

almindor / etherwall

Ethereum QT5 Wallet
GNU General Public License v3.0
143 stars 59 forks source link

Unknown error after leaving wallet to sync for a few hours #51

Closed mascondante closed 7 years ago

mascondante commented 7 years ago

The error popup is blank as of 2.0.1. Nothing in the text field. Just a standard title bar and ok button. Not using thin client. Noticed 2.0,2 just dropped. Going to give that version a spin and see what happens.

mascondante commented 7 years ago

Also your latest version post claims geth 1.6.7 but the title bar in 2.0.2 still says geth 1.6.6.

almindor commented 7 years ago

Which version of OS (windows/?) is this?

Can you provide a screenshot?

What exactly happens? Etherwall starts (in full node mode) and you let it sync then you get an empty error?

I'll check on the bundled geth, maybe I put the old one in by accident.

almindor commented 7 years ago

Just checked and the packaged version should be 1.6.7.

Can you look at your geth path in settings? Is it pointing to geth.exe in the same folder as Etherwall is or somewhere else?

mascondante commented 7 years ago

Windows 10 Creator's update x64. Here's the screenshot. It happens while syncing. I haven't been able to fully sync yet partially because when this error throws I believe geth stops working as when I notice, close and reopen there's noticeably more blocks but I could be wrong.

As far as geth the newer version of Etherwall retained the old geth directory set in 2.0.1. I adjusted and now it's reflecting correctly.

almindor commented 7 years ago

Is there any additional info in the logs? See logs/app

mascondante commented 7 years ago

Nothing I can see in this session's app log. Do you have logs set to write out to a file somewhere per session? Catching a shy bug that totally freezes the app would be hard to catch otherwise.

I will say I've noticed if I overclock my gpu too high it will stop responding when the GPU resets. But in that case there is no popup. I doubt the two issues are related but I thought I would let you know about that as well. That's more low priority because it's the user's responsibility to keep their card from crashing rather than the developer of an app redoing their code because of user error.

mascondante commented 7 years ago

Okay I was able to catch a log without the app totally freezing. I don't spot anything but maybe you'll have better luck. https://ghostbin.com/paste/78cwo

UGatgithub commented 7 years ago

The last logged action relates to the currency load function which reminds me somehow on the issue I have with the currency load: https://github.com/almindor/etherwall/issues/37 Just an idea, could you create a debug where the currency load can be disabled to check if there is a connection between the freeze and the currency load?

almindor commented 7 years ago

Hmm nothing really shows up in the log. When you get the freeze you get a popup and the app becomes unresponsive correct?

I don't think it has anything to do with currency loading, that action is periodic on purpose. I don't even think the error got logged.

mascondante commented 7 years ago

Okay it happened again. I noticed the geth log was spitting out something different than the usual imported chain whatever stuff. I scrolled to where that transition from normal activity stops and changed the window size to get a better screenshot (since the geth window won't let me copy to clipboard). The app then froze the moment I tried to scroll after resizing the window but I was able to take this screenshot.

almindor commented 7 years ago

OK so this is a geth bug. Can you take the screenshot and report on https://github.com/ethereum/go-ethereum ?

You can also try to reproduce without Etherwall by just running geth from commandline, but be sure to specify same parameters (you can see them in the app log).

I'll keep this issue open for a while in case we find something else, but it seems geth crashes on your machine.

mascondante commented 7 years ago

Hey sorry about the delay. I haven't opened an issue with the Ethereum folks but I did read the diff files from 2.0.2 to 2.0,4. It seems (from my very limited understanding) you've got the code adjusted to catch any mystery bugs. I just upgraded to 2.0.4 now. If I find that illusive bugger I'll report it back here.

mascondante commented 7 years ago

Okay caught it. Geth Log App log

almindor commented 7 years ago

Hmm seems another geth bug yeah. This one seems to have happened on a syscall. Can you send the geth log to https://github.com/ethereum/go-ethereum ? Maybe search if you can find a similar issue already opened first.