RC2 Exits After Initialization #11171
Comments
|
For the record, I just installed RC3 and it exhibits the same problem. |
|
Please post the entire debug.log file. The snippet provided does not give anything meaningful. |
|
Below is the entire debug output from my latest attempt to start rc3: 2017-08-29 19:37:52 Bitcoin version v0.15.0rc3 |
|
The issue won't be contained in debug.log if its crashing with like a segfault, won't log anything to the debug log during the crash, which looks like might be the case here because the log just ends abruptly, maybe try running in gdb? https://gist.github.com/laanwj/29bc141fb8d10608651c |
|
Well, I can confirm that bitcoind.exe does NOT appear to crash - this seems to be an issue only with bitcoin-qt.exe. Sadly, it does not appear to be possible for me to debug this binary with either of the GDBs I have installed - CygWin and MinGW. Both report that the file is not a recognized executable format. It does appear to be a segfault error, I think - if I start bitcoin-qt from the command line, it will restart continuously after each initialization. |
|
Any crash messages? Wonder if this is related to 9683 and 9883 |
|
No crash messages, nothing ever gets printed on STDOUT - but looking at the windows logs shows that the error is definitely an access violation, so probably a null pointer thing. I am going to try to install a debugger on windows that I can use to attach to the process and see if I can figure out what's going on as soon as I get a chance. |
|
Also please try launching with |
|
Wow! Running with '-resetguisettings' fixed the problem! Thanks :) |
|
Good |
|
@jonasschnelli looks like this was the same problem as #7869 again then, have you got anywhere with the cause? |
|
@xyzzy099 Did you have multiple monitors? If so, did you disconnect one monitor before you started Bitcoin Core? |
|
I did not have multiple monitors - but I have accessed the machine in question remotely (which windows, I believe, may see as another monitor), and have stopped/started Bitcoin-qt via the remote session. As an additional data point, when I was still running 0.14.2 I noticed that the Bitcoin-qt window had started to always open in the extreme lower right-hand of the screen consistently, which is not default behavior, and persisted in opening in that location no matter where the window was when I closed it. Maybe meaningless, but I thought I should mention it since it seemed odd to me at the time. |
|
Additionally, I should mention that, at least in my case, the window was definitely NOT opening off-screen. The client was crashing with a memory access violation consistently, |
|
Since |
|
@xyzzy099 Do you have any windows logs of the crash that show a memory access violation? |
|
Yep. Lots of them, just like this one: Faulting application name: bitcoin-qt.exe, version: 0.15.0.0, time stamp: 0x59a3d3e7 |
|
For completeness, I should add that in some of the log entries the "faulting module path" is " C:\Windows\SYSTEM32\ntdll.dll". |
|
I've been looking into this much more just now, and I found something interesting. So normally we should see this line: |
|
Reopening under the assumption that this is not solved. |
|
I have a similar crash bug on Windows 10 64 with 0.15-rc3. |
|
@wostl please open a separate issue with a bit more info, its hard to tell whether that is the same issue or not :) |
|
"-resetguisettings" fixed the crashbug for me too (bitcoin-0.15.0-win64). |
|
For anyone who comes across this in the future, please post your GUI settings before doing |
|
The registry key in windows is
Barring some incredibly ugly memory corruption we can rule that out, it's checked in the beginning of that function. |
|
I upgraded from 0.14.2-uasfsegwit1.0 to 0.15.0-rc3, and then to 0.15.0. Both 0.15.0 crashed on the splash screen just before the GUI used to appear. Tray icon was already there. I know that my cache settings were raised (to either 2 or 4GB). UPNP and incoming connections were set. |
|
@wostl did you have a proxy set? |
|
Definitely no proxy. |
|
Closing, should be fixed by #11335. |
and others
I installed RC2 on my Windows7 box, and it exits shortly after initialization consistently. The debug log contents look OK, with the only errors contained in the snippet below:
2017-08-27 14:00:58 GUI: PaymentServer::LoadRootCAs: Loaded 56 root certifica
es
2017-08-27 14:00:58 tor: Error connecting to Tor control socket
2017-08-27 14:00:58 tor: Not connected to Tor control port 127.0.0.1:9051, tryi
g to reconnect
2017-08-27 14:00:58 GUI: TransactionTablePriv::refreshWallet
2017-08-27 14:00:59 trying connection 79.195.178.192:8333 lastseen=366.6hrs
2017-08-27 14:00:59 Added connection peer=0
2017-08-27 14:01:00 tor: Error connecting to Tor control socket
2017-08-27 14:01:00 tor: Not connected to Tor control port 127.0.0.1:9051, tryi
g to reconnect
2017-08-27 14:01:03 tor: Error connecting to Tor control socket
2017-08-27 14:01:03 tor: Not connected to Tor control port 127.0.0.1:9051, tryi
g to reconnect
2017-08-27 14:01:04 connection to 79.195.178.192:8333 timeout
2017-08-27 14:01:04 trying connection 81.163.206.173:8333 lastseen=175.4hrs
2017-08-27 14:01:04 connection from 213.5.31.38:54224 accepted
2017-08-27 14:01:04 Added connection peer=1
2017-08-27 14:01:04 connection from 52.192.180.114:40814 accepted
2017-08-27 14:01:04 connection from 54.191.174.46:38180 dropped (banned)
2017-08-27 14:01:04 received: version (106 bytes) peer=1
2017-08-27 14:01:04 sending version (102 bytes) peer=1
2017-08-27 14:01:04 send version message: version 70015, blocks=482210, us=[::]
0, peer=1
2017-08-27 14:01:04 sending verack (0 bytes) peer=1
2017-08-27 14:01:04 receive version message: /bitcoin-seeder:0.01/: version 600
0, blocks=350000, us=73.119.168.246:8333, peer=1
2017-08-27 14:01:04 added time data, samples 2, offset -209 (-3 minutes)
2017-08-27 14:01:04 sending alert (168 bytes) peer=1
2017-08-27 14:01:05 received: verack (0 bytes) peer=1
2017-08-27 14:01:05 sending ping (0 bytes) peer=1
2017-08-27 14:01:05 socket closed
2017-08-27 14:01:05 disconnecting peer=1
The text was updated successfully, but these errors were encountered: