bitcoin-qt crash while performing transaction #2550

bintcoin-qt v0.8.0-228-gce8de31-dirty-beta randomly crashes while sending a transaction. The created transaction is not send to the network, but is inside the transaction tab visible. The bitcoins are subtracted from wallet.

Full Crashlog: https://gist.github.com/tripplet/7c4f9c5809516cc52aba

EDIT: Interestingly the transaction has just been verified - accepted in a later block.

EDIT - AGAIN: Now bitcoint-qt crashed again and does not start any more it allways crashes during startup

Crashlogs: https://gist.github.com/tripplet/8f586b111fd86e2ade59 https://gist.github.com/tripplet/891f80fd357c93572a34 https://gist.github.com/tripplet/a3ea11ffbd142bd67410

I'm not sure what the problem is, hopefully someone can tell me more.

Can you upload the debug.log somewhere? There may be more info in there.

On first look it looks like a leveldb issue, it is calling abort.

Thread 7 Crashed:
0   libsystem_kernel.dylib          0x00007fff807c1212 __pthread_kill + 10
1   libsystem_c.dylib               0x00007fff8b216b54 pthread_kill + 90
2   libsystem_c.dylib               0x00007fff8b25adce abort + 143
3   libsystem_c.dylib               0x00007fff8b25be2a __assert_rtn + 146
4   org.bitcoinfoundation.Bitcoin-Qt    0x0000000100227158 leveldb::InternalKeyComparator::Compare(leveldb::Slice const&, leveldb::Slice const&) const + 218
5   org.bitcoinfoundation.Bitcoin-Qt    0x0000000100239096 leveldb::(anonymous namespace)::MergingIterator::FindSmallest() + 152
6   org.bitcoinfoundation.Bitcoin-Qt    0x00000001002393f6 leveldb::(anonymous namespace)::MergingIterator::Next() + 264

Your right, I deleted the local blockchain and bitcoin-qt worked again - but I switched to a different client because of the frist randomly appearing bug with sending transactions. The debug.log shows nothing out of the ordinary, I'm not uploading it, because of all my transaction-ids in it and the fuzz to remove them all.

There is really nothing we can do to help debugging if you don't trust us with the debug.log output (you could send it privately or encrypted if you want)

Good that removing the block chain solved it. These leveldb corruptions on OSX are strange. Maybe it has something with the file descriptor issue.

You got mail

@laanwj Anything useful?

I could not reproduce this bug. Must be a special configuration.

Problems reaches surface at: Assertion failed: (internal_key.size() >= 8), function ExtractUserKey, file ./db/dbformat.h, line 96.

I found no error messages or strange things in the debug.log he sent. @jonasschnelli where do you get/see that assertion?

@laanwj crashlogs line 19.

Duplicate; hopefully fixed by the "don't use too many file descriptors" fix.