Quote from: etotheipi on July 07, 2012, 05:00:58 AM

Quote from: etotheipi on July 06, 2012, 05:11:39 PM

Quote from: Gladamas on July 06, 2012, 04:45:31 PM

Hey etotheipi, thanks for your work on Armory. Grin

I love the new features.

Every so often Armory crashes after running for a couple of hours. I'm not sure if this is my computer's fault, or a bug in the software. I am mining for BTC (on the GPU) and LTC (on the CPU) on the same computer.

...

While I work on updating 20k lines of python code with proper logging calls, I'll load up Armory in my Windows VM and leave it running to see if I can replicate the behavior in the debugger.

So I loaded Armory in my Win7-64bit VM with 2GB of RAM in online mode. I executed one transaction, then went to my development desktop and forgot about it. 7 hours later, no crash. Anyone who is experiencing this crash have any hints about what I can do to trigger it? Are you doing anything before it crashes? This is going to be a tough bug without any way to replicate it!

Ah, I forgot to mention, every time I start an Armory instance that crashes later, it won't receive (show or give any indication of) a new transaction coming to one of its Bitcoin addresses. The transactions are in the blockchain but won't show up. I forgot if it ahows the correct block number or not, though. Perhaps the crash occurs when Armory receives a second transaction (after the first that it didn't show?) Just a WAG.