Ethereum wallet > 0.7.4 immediately closes when launching

[ngburke]

Node type: geth
OS: windows 10 64-bit
Network type: main
Mist version: 0.7.5+

I had previously been running on an old version of Ethereum-Wallet r0.5.2 with no problems. With the fork coming up, I wanted to upgrade. Downloaded r0.8.1 win-64 and fired it up and it immediately terminated (no splash screen at all). After a binary search on the version that this behavior started, i found I was able to successfully launch r0.7.4, but 0.7.5+ exhibited the same problem.

I tried a number of things, first deleted the chaindata in the Ethereum folder. Using the geth packaged with r0.8.1, I was able to re-sync the blockchain no problem. Unfortunately, the Ethereum-Wallet.exe still instantly crashed. I then got rid of the AppData/Roaming/Mist folder and re-launched 0.8.1 and 0.7.5, stiil the same problem.

I deleted /AppData/Roaming/Mist/node.log, and when I launch a working version (0.7.4), a new node.log appears. When deleting this again and running 0.8.1 or 0.7.5 no node.log file is even created, Looking for some help please, let me know if I can provide more information.

[luclu]

Thank you for this neat issue description. 👍
Could you please start Ethereum-Wallet.exe from the terminal and post its output?

[ngburke]

When launching from the command line, it shows no output in the terminal - just a blank line. When I press return a second time, I'm back to the command prompt. I see a process called 'Electron' in task manager briefly when launching from the command line, but it looks to be immediately killed.

[luclu]

hmm, could you append it with --loglevel trace?

[ngburke]

Tried that, same result no output. Here is a screenshot showing the 0.8.1 w/ trace (blank) vs. 0.7.4 (looks nice).

[luclu]

This seems to be related to node.js not being able to load some library within the electron framework: electron/electron#6437 (comment)

[ngburke]

I tried downloading node.js v6.3.0 and it appears to have 'started' (can get to the node command prompt). I can confirm that I am running wireless LAN which looks similar to the setup that the other person at nodejs/node#5588.

Is there anything I can do to work around this? It was non-obvious to me how node.js and the ethereum wallet are dependent (I didn't seem to have node.js installed on my system before, maybe its something that gets bundled at build?). Is the problem still considered open at this time?

[mpunisher]

I have the same issue
any help please

[luclu]

We might have to wait for electron/electron#6437 for now. Perhaps they will come up with some workaround - otherwise the next release should fix this hopefully.

[netprofit]

same problem for me too: node starts ok, finds peers, starts syncing and then crashes. Using Mist 0.8.1, which I installed yesterday (OS windows 10 64bit) Y.day everything was working fine. Problem only started this morning.

Only difference to what's reported by others is that when I first started the program this morning the wallet opened and I got this message:

404
File not found
The site configured at this address does not contain the requested file.
If this is your site, make sure that the filename case matches the URL.
For root URLs (like http://example.com/) you must provide an index.html file.
Read the full documentation for more information about using GitHub Pages.
GitHub Status — @githubstatus

I then closed the program and when I restarted it, I got the crashing on launch problem.

[ngburke]

I'm concerned with the fork happening that I'll end up on the wrong side of that if I don't update to 0.8.1 soon. Can someone educate me on whether using a working version 0.7.4 will by default mean I am on the 'fork' side of the fence? Put another way, if I do nothing with my current holdings (no wallet update etc.) will I be ok?

[luclu]

@ngburke I you had any version of Mist/Ethereum-Wallet <0.8.1 syncing the block transition from bock 1,919,999 to 1,920,000 your node will now be on the non-HF chain - regardless if you run 0.8.1 after the transition. In that case you will have to remove the chaindata folder and initiate a full resync AFAIK.

Unfortunately this means you cannot use any older version until this issue is fixed.

[luclu]

@ngburke could you please try to backup the %appdata%\Mist folder and delete the mist.lokidb file?

[ngburke]

I did a search in %appdata%\Roaming\Mist for mist.lokidb and found no file with that name.

[netprofit]

@ngburke the file is definitely there (in the roaming folder)

@luclu having deleted the mist.lokidb file, my wallet (0.8.1 running on Windows 10 64 bit) opened successfully, so the fix works (thanks!) but having closed the wallet and tried to restart it, the problems (wallet crashing immediately following synchronisation or the appearance of an 404 error message - see my earlier post - or the synchronisation process not even starting) reoccur and so it's necessary to delete the mist.lokidb file again in order for the launch process to work and the wallet to open.

[mpunisher]

after deleting mist.lokidb the mist open opened successfully (WIN7 64)
thanks

[luclu]

@ngburke ok, I just wanted to make sure #1002 is not related.

---

@netprofit @MHaythem you are experiencing issue #1002.
Please follow that issue as this one is unrelated. You can unsubscribe on the right sidebar if you want.

[netprofit]

@luclu ok, thanks. Nevertheless, your suggested fix (delete mist.lokidb) did work.

[ngburke]

Confirmed fixed in 0.8.4

[lock]

This thread has been automatically locked because it has not had recent activity. Please open a new issue for related bugs and link to relevant comments in this thread.