Quote from: trev on August 31, 2015, 05:36:02 AM

Quote from: goatpig on August 26, 2015, 06:40:30 AM

What's the total size of your DB? The headers DB alone?

https://github.com/etotheipi/BitcoinArmory/blob/ffreeze/cppForSwig/mdb/mdb.c#L588

Reduce this value to 16MB and rebuild a new DB with that, see if it suffers from the bad_alloc.

I reduced MAX_MAPSIZE_INCEREMENT from 256MB to 16MB, re-compiled, and --rebuild.
The databases are now:
20819968 2015-08-31 00:57 blocks
107724800 2015-08-31 00:57 headers
After a couple of days of uptime I got the std::bad_alloc crash.

I'm running an identical copy of bitcoin-qt/Armory on a newer desktop that has 16GB dram.
I got the std::bad_alloc crash on that machine too, just like the laptop.

I also got the std::alloc crash when sending to a "normal" wallet.

In one instance so far, I started Armory at 23:50 and sent BTC at 00:10 and got std::alloc.
Is there any code in Armory that uses "current time - previous time" and doesn't handle
a negative value?

Comment out this line:

https://github.com/etotheipi/BitcoinArmory/blob/ffreeze/ArmoryQt.py#L2619

It will prevent the ZC container from parsing any new tx. This is the most likely culprit atm.