Bitcoin-Qt OS X 10.8 new user crashes on startup since 0.9.2 #4877

Hello!

I'm a new Bitcoin user, and I am unable to get Bitcoin-Qt to work on my Mac OS X 10.8.5 system: When I start the client, it crashes during the "Loading Addresses" part of the startup process.

I've tried 0.9.2, 0.9.2.1, and 0.9.3rc1, all of which crash. Versions 0.8.6, 0.9.0, and 0.9.1 all work: It was able to start up, it recognized bootstrap.dat, and it started importing blocks from disk. Here's what I did to test:

1. Delete the contents of the ~/Library/Application Support/Bitcoin directory, except for bootstrap.dat.
2. Download the Bitcoin-Qt .dmg image, and copy to /Applications
3. Launch Bitcoin-Qt.

At this point, the splash screen appears for ~30 seconds, and then one of two things will happen: Either the app will bring up the Wallet window, and start loading transactions from disk, or the app will crash. Normally, the splash screen says "Loading Addresses" at the time of the crash.

FYI, my bootstrap.dat was download via torrent less than two hours ago. I get the same crash-y behavior without bootstrap.dat.

I've collected the OS X crash log and the debug.log from my attempts at running 0.9.2 and 0.9.3rc1, and have made them available here:

https://dl.dropboxusercontent.com/u/18635216/bitcoin%20issue%204877.zip

One note: In the debug log, I saw the message "Invalid or missing peers.dat; recreating". peers.dat never appeared in the filesystem before the crash.

Looks like it crashes in QSslSocket::systemCaCertificates(). I remember seeing this before on a SSL version conflict, where the core was using another instance of OpenSSL from Qt.

8   libsystem_c.dylib                   0x00007fff86c1268b exit + 15
9   libcrypto.1.0.0.dylib               0x000000010739ab15 OPENSSL_config + 133
10  QtNetwork                           0x0000000106ad0103 QSslSocketPrivate::ensureLibraryLoaded() + 131
11  QtNetwork                           0x0000000106ad08d0 QSslSocketPrivate::systemCaCertificates() + 32
12  QtNetwork                           0x0000000106acb97e QSslSocket::systemCaCertificates() + 14

@theuni OpenSSL and Qt5 are both static on MacOSX right? Do you know why is it trying to load a dynamic library here?

Can you try running with the command line option -rootcertificates= (ie, empty) or putting rootcertificates= in bitcoin.conf? This avoids the crashing call. (it may still crash later)

@laanwj libcrypto/libssl are shared on osx because qt was shared. Using static for both would've meant duplicating them, so instead we built shared libs that they both point to. Qt (and now openssl) is now static in master when built with depends, and releases will be once the gitian changes go in. @akkornel Would you be willing to try a build from the current master branch? If so, the file linked in #4854 would be a good test.

All the files I generated in this reply are located here:

https://dl.dropboxusercontent.com/u/18635216/bitcoin%20issue%204877-1.zip @theuni I got the binary from https://bitcoincore.org/cfields/bitcoin-qt-tabletfix-6ee78938e. I wasn't sure how you wanted me to run it, so I did chmod a+x on the file and ran it through Terminal. When I did, I got some output on standard output or standard error, and it did crash when launching. I prefixed the files with the string "Version 6ee78938e (clean)". @laanwj I created a file at path ~/Library/Application Support/Bitcoin/bitcoin.conf, only containing the line "rootcertificates=". I removed everything from the Bitcoin directory except for bitcoin.conf and bootstrap.dat. I then tried running the binary that I used with the test for @theuni. This time, the application did run, and started importing the block chain from bootstrap.dat. At that point, I quit the application. There was no output on standard output/error, and there was no crash log (since it didn't crash), but I did save the debug.log. The string prefix is "Version 6ee78938e (noroot)".

Out of curiosity. I also tried with 0.9.1, and that also worked, as long as bitcoin.conf was present. I didn't grab the debug.log, so let me know if you need it!

Issue has been resolved a long time ago - thanks for cooporating to fix it