recent crashing #2674

The code was fine, even rolling back to previous backups will not prevent crash Also re-installed app..

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x0000000000000000, 0x0000000000000000

Application Specific Information: Assertion failed: (pfork != NULL), function SetBestChain, file src/main.cpp, line 1742.

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 libsystem_kernel.dylib 0x94295a6a __pthread_kill + 10 1 libsystem_c.dylib 0x93417b2f pthread_kill + 101 2 libsystem_c.dylib 0x9344e4ec abort + 168 3 libsystem_c.dylib 0x9345cd2b __assert_rtn + 326 4 com.yourcompany.Bitcoin-Qt 0x000d1656 SetBestChain(CValidationState&, CBlockIndex*) + 2454 5 com.yourcompany.Bitcoin-Qt 0x000d3526 ConnectBestBlock(CValidationState&) + 598 6 com.yourcompany.Bitcoin-Qt 0x0011cbd7 AppInit2() + 16839 7 com.yourcompany.Bitcoin-Qt 0x000229e3 main + 7603 8 com.yourcompany.Bitcoin-Qt 0x0001f921 start + 53

The " Assertion failed: (pfork != NULL), function SetBestChain, file src/main.cpp, line 1742. " error

is the same as #2405 & #2426

Were you running 0.8.1 or 0.8.2 when the crash happened?

It would also be helpful if you can tell us which version of OS X your running.

osx 10.8.3 The version is the latest on the site 0.8.1 did not know there was an 8.2 version……….

On May 20, 2013, at 1:25 PM, Michael Ford notifications@github.com wrote:

This error message

" Assertion failed: (pfork != NULL), function SetBestChain, file src/main.cpp, line 1742. "

is the same as #2405 & #2426

Were you running 0.8.1 or 0.8.2 when the crash happened?

It would also be helpful if you can tell us which version of OS X your running.

— Reply to this email directly or view it on GitHub.

0.8.2 is currently in the release candidate stage, see https://bitcointalk.org/index.php?topic=201124.0

It contains code changes which should hopefully fix the issue your having.

nope…. still crashing.

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x0000000000000000, 0x0000000000000000

Application Specific Information: Assertion failed: (pfork != NULL), function SetBestChain, file src/main.cpp, line 1764.

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 libsystem_kernel.dylib 0x94295a6a __pthread_kill + 10 1 libsystem_c.dylib 0x93417b2f pthread_kill + 101 2 libsystem_c.dylib 0x9344e4ec abort + 168 3 libsystem_c.dylib 0x9345cd2b __assert_rtn + 326 4 org.bitcoinfoundation.Bitcoin-Qt 0x000d23d3 SetBestChain(CValidationState&, CBlockIndex*) + 2211 5 org.bitcoinfoundation.Bitcoin-Qt 0x000d4128 ConnectBestBlock(CValidationState&) + 824 6 org.bitcoinfoundation.Bitcoin-Qt 0x0012645a AppInit2(boost::thread_group&) + 22154 7 org.bitcoinfoundation.Bitcoin-Qt 0x00022a80 main + 7504 8 org.bitcoinfoundation.Bitcoin-Qt 0x0001fd51 start + 53

On May 20, 2013, at 2:10 PM, Michael Ford notifications@github.com wrote:

0.8.2 is currently in the release candidate stage, see https://bitcointalk.org/index.php?topic=201124.0

It contains code changes which should hopefully fix the issue your having.

— Reply to this email directly or view it on GitHub.

If the linked issues are anything to go by, it is an corruption in an index data structure and passing -reindex should solve this issue for you.

Yes it was….

But I have noticed the 'indexes' get corrupted a lot on OSX, even if the drive and files 'check out'. I suspect some sort of buffer flushing issue for the database, seen this before under osx where I have a MASSIVE database and the software shuts down gracefully, but then the database ends up corrupted, normally I have to force flush before the shutdown.

Same with NAS on osx, you have to issue a "fake" shutdown and cancel to correctly flush the buffers sometimes.

On May 20, 2013, at 4:34 PM, Wladimir J. van der Laan notifications@github.com wrote:

If the linked issues are anything to go by, it is an corruption in an index data structure and passing -reindex should solve this issue for you.

— Reply to this email directly or view it on GitHub.

0.8.2 has some OSX related fixes in that area, can you try and see if this mess happens again?

K I will keep 0.8.2 running to see if it trashes the new database.

On May 24, 2013, at 2:41 PM, Philip Kaufmann notifications@github.com wrote:

0.8.2 has some OSX related fixes in that area, can you try and see if this mess happens again?

— Reply to this email directly or view it on GitHub.

Please open a new issue if this is still a problem with 0.8.2