I can add that there is definitely some kind of race condition when it comes to Armory reading the blockchain database while the Satoshi client writes to it. I have several times seen Armory crash in that situation. It typically happens when the Satoshi client is catching up, and I start Armory while this is happening. Then suddenly Armory crashes. But it is rare, I cannot reproduce it on demand, and I was stupid enough not to save info about the crash (not that it seemed particularly informative, I think it was just a segfault with no info about where in the code it happened).
Definitely, Armory doesn't like "drinking from the firehose" if Bitcoin-Qt is still updating (and 0.84.1 will detect this condition and produce a warning). I'm about to run off for an hour, so I put a one-hour sleep command after my load-blockchain call in my code, to try to guarantee there is a new block by the time it "finishes" scanning. I haven't had time to hunt down the code path, but at least if I can reproduce what OpenYourEyes was seeing, that's a great start.
so i just downloaded 0.84. upon launch i get this error: the specified module could not be found. LoadLibrary (pythondll) failed.
also something about python27.dll error
Bizarre. Can you try manually deleting "C:\Program Files (x86)\Armory" and then reinstall?
Of course, I just had my first crash of Armory in Windows, after it was running for about a day! Gah, everything looks so good, then starts falling apart!
that won't erase any wallet data will it? i migrated in a satoshi wallet.
Show Posts
