Topic: Armory Crashing Bug (Read 918 times)
Armory keeps crashing all of the fucking time, so annoying.
I'm a new user of Armory, trying 0.90, and it's crashing consistently before I have even imported my wallet. I've already had Bitcoin-QT running to download all the blocks. I can send you my log files, as well, if you'd like.
Would like the logs indeed. Curious to see which bug this is. It can't be the same as justusranvier's, for you have no wallet loaded.
Scratch that. It still crashes while just sitting there. Even without a wallet imported.
I'm a new user of Armory, trying 0.90, and it's crashing consistently before I have even imported my wallet. I've already had Bitcoin-QT running to download all the blocks. I can send you my log files, as well, if you'd like.
Luckily, one of the things I'm doing in 0.91-beta is fixing all the issues with Armory that cause it to slow down when huge wallets are loaded. One of those things is the fact that the main thread processes new blocks, and freezes everything while it's processing. If it takes more than 20s, then you can end up with this error. If we stick it in another thread, and don't update the GUI until it's done, then it doesn't matter how many addresses you have, you will just be notified of new blocks with a delay.
Also, there's just some missing optimizations that lead it to be so slow, anyway. Those will be fixed first.
Finally, I may be able to disable the unclean shutdown thing. It just occurred to me that I can rewrite all the address history only after each block when it's in a good state. If it crashes during a block processing, it will restore the previous state. And Armory will rescan the last 2016 blocks anyway.
Also, there's just some missing optimizations that lead it to be so slow, anyway. Those will be fixed first.
Finally, I may be able to disable the unclean shutdown thing. It just occurred to me that I can rewrite all the address history only after each block when it's in a good state. If it crashes during a block processing, it will restore the previous state. And Armory will rescan the last 2016 blocks anyway.
Send us the full log, and the cpplog too.
https://bitcoinarmory.com/about/contact-us/Your contact page mentions GPG keys, which is an excellent idea, but I don't actually see any listed or on any keyservers.
Yeah that failed pretty hard, I'll try to get it fixed. Thanks for the report.
Send us the full log, and the cpplog too.
https://bitcoinarmory.com/about/contact-us/Your contact page mentions GPG keys, which is an excellent idea, but I don't actually see any listed or on any keyservers.
I dont see any either. Send us the full log, and the cpplog too. I may find some hint in there.
This happens often enough that I don't get any benefit from the changes in 0.90. I almost never have a clean shutdown.
I don't see any evidence of problems in bitcoind's logs around the time this happened.
Code:
2013-12-25 21:57 (INFO) -- armoryengine.py:10634 - Received new block. 0000000000000002183ed6df1f380c9333f32b1f779e404e60a11bff7968904c
2013-12-25 21:57 (INFO) -- ArmoryQt.py:4781 - New Block! : 276995
2013-12-25 21:57 (INFO) -- ArmoryQt.py:4805 - Current block number: 276995
2013-12-25 22:12 (INFO) -- ArmoryQt.py:4781 - New Block! : 276996
2013-12-25 22:12 (INFO) -- ArmoryQt.py:4805 - Current block number: 276996
2013-12-25 22:14 (INFO) -- armoryengine.py:10634 - Received new block. 0000000000000000f5263c79ac83062cd24f2c71692de09fc937735a0abef523
2013-12-25 22:14 (INFO) -- ArmoryQt.py:4781 - New Block! : 276997
2013-12-25 22:14 (INFO) -- ArmoryQt.py:4805 - Current block number: 276997
2013-12-25 22:33 (INFO) -- ArmoryQt.py:4781 - New Block! : 276998
2013-12-25 22:33 (INFO) -- ArmoryQt.py:4805 - Current block number: 276998
2013-12-25 22:41 (INFO) -- ArmoryQt.py:4781 - New Block! : 276999
2013-12-25 22:41 (INFO) -- ArmoryQt.py:4805 - Current block number: 276999
2013-12-25 22:48 (INFO) -- armoryengine.py:10634 - Received new block. 0000000000000001b8a1691057cd6639e56224d99f7f7d80e7b61f55be52d931
2013-12-25 22:48 (INFO) -- ArmoryQt.py:4781 - New Block! : 277000
2013-12-25 22:48 (INFO) -- ArmoryQt.py:4805 - Current block number: 277000
2013-12-25 22:49 (INFO) -- ArmoryQt.py:4781 - New Block! : 277001
2013-12-25 22:49 (INFO) -- ArmoryQt.py:4805 - Current block number: 277001
2013-12-25 22:51 (INFO) -- armoryengine.py:10634 - Received new block. 000000000000000107ddda65ee3ae1c6d67a96e0c5438e15d5567170ddd849fe
2013-12-25 22:51 (INFO) -- ArmoryQt.py:4781 - New Block! : 277002
2013-12-25 22:51 (INFO) -- ArmoryQt.py:4805 - Current block number: 277002
2013-12-25 23:00 (ERROR) -- armoryengine.py:12372 - Waiting for BDM output that didn't come after 20s.
2013-12-25 23:00 (ERROR) -- armoryengine.py:12373 - BDM state is currently: BlockchainReady
2013-12-25 23:00 (ERROR) -- armoryengine.py:12374 - Called from: armoryengine.py:12563 (94868342)
2013-12-25 23:00 (ERROR) -- armoryengine.py:12375 - BDM currently doing: ZeroConfTxToInsert (85534452)
2013-12-25 23:00 (ERROR) -- armoryengine.py:12376 - Direct traceback
2013-12-25 23:00 (ERROR) -- armoryengine.py:12378 - Traceback:
Traceback (most recent call last):
File "/usr/lib64/armory/armoryengine.py", line 12368, in waitForOutputIfNecessary
return self.outputQueue.get(True, self.mtWaitSec)
File "/usr/lib64/python2.7/Queue.py", line 176, in get
raise Empty
Empty
2013-12-25 23:00 (ERROR) -- armoryengine.py:13289 - ErrorOut var over-represented number of errors!
2013-12-25 23:00 (ERROR) -- ArmoryQt.py:4725 - Detected Bitcoin-Qt/bitcoind not synchronized
2013-12-25 23:00 (ERROR) -- ArmoryQt.py:4726 - New blocks added in last 5 sec: 277002
I don't see any evidence of problems in bitcoind's logs around the time this happened.
Jump to: