Crash on Mac with "Assertion failed: (pfork != NULL)" #2405
Comments
|
Exactly the same issue. Upgraded from 0.8.0-beta. |
|
I have encountered the same issue with version 0.8.1 mba:MacOS fredrik$ ./Bitcoin-Qt |
|
@gavinandresen As I know you are using Mac, can you take a look here :). |
|
Gavin posted a possible fix here: https://bitcointalk.org/index.php?topic=154516.msg1665186#msg1665186 I tried it, but the client still crashed. I moved my ~/Library/Application Support/Bitcoin directory aside and ran the client. It downloaded the blockchain again and didn't crash. Perhaps that's the easiest fix. Now I just have to import my wallet. |
|
hank: the link you pasted talks about cleaning the data directory after the change in its structure, it shouldn't really solve the issue. In #2426 there are two suggestions, I preferred using -reindex option, the two issues should be merged. |
|
I just finished doing a -reindex. It solved the problem for me. |
|
I'd like to see a debug.log for when this happens, before doing a -reindex. |
|
sipa: I wouldn't know how to reproduce, may be worth editing first post asking for that so next people who search the issue can keep the debug.log file. |
|
@gavinandresen It was a while ago the crash happened for me. I had recently installed the app and the index had finished syncing. I Had gotten a small transfer, everything was working fine. I later had some issues not related to bitcoin-qt. what I can remember the mac did not shutdown cleanly. Then during startup of bitcoin-qt the application crashed. This was some time ago, can't remember exactly what happened. I will make sure to write things down if they happen again. Thanks for looking in to the issue! |
|
Notice that I didn't have any crash (IIRC) and I've been running the client for several days, maybe a couple weeks, after the update. I update the chain every other day or less often, on such an update the Qt client just didn't start anymore. Reindexing fixed the issue. |
|
I upgraded from the previous beta version I think. After quitting the installed version, I installed 0.8.1, and tried to start it. It crashed over and over again with the error at the top. I then tried moving my bitcoin Library directpry aside and letting it download the entire blockchain again. That seems to have fixed the issue. |
|
Closing this as "corruption likely caused by running out of file descriptors". |
|
So, in Bugzilla terms, that's a WONTFIX? I was able to recover by removing everything from ~/Library/Application Support/Bitcoin then copying in a very old backup of my wallet.dat. After that the client ran normally, but took several days to re-download the block chain. |
|
@Polyergic No, it's a "unknown if fixed or not". We assume it's a corruption of your database that was caused by a known bug that is now fixed in HEAD (but is not in a released version yet). So feel free to reopen or comment here if it would happen again after updating. Also, next time, you can recover using -reindex (which just imports the block data you already hvae and revalidates it, but doesn't redownload it). |
|
No that is no WONTFIX, it is a (hopefully) HAVEFIXED by one of the recent patches :). |
|
Oh, I see, there just wasn't a comment here about the patch. Thanks! |
Closed
Closed
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Mac OS X 10.7.5
Bitcoin-Qt 0.8.1
Recently upgraded to Bitcoin-Qt 0.8.1, the new version had started over rechecking the entire block chain. At about 90% caught up the system crashed (kernel panic / grey screen of death).
After the system crash, Bitcoin-Qt would crash on launch. A quick search for the problem suggested reinstalling, so I reinstalled to a different folder, and the new installation also crashed on launch. I didn't look at the crash report before reinstalling, now both installs crash with this error:
"Assertion failed: (pfork != NULL), function SetBestChain, file src/main.cpp, line 1742".
I also have 0.6.3 installed, but have not launched it since the first install of 0.8.1.
EDIT: If you are also having this problem, please share your
debug.loghere before attempting to fix the problem.Full crash report:
The text was updated successfully, but these errors were encountered: