Quote from: bitcool on February 25, 2015, 11:54:24 PM

Quote from: goatpig on February 25, 2015, 10:50:07 PM

Quote from: bitcool on February 25, 2015, 10:31:26 PM

The latest version has memory leaks, badly. It consume 15.8 GB of my 16 GB Windows memory, every time.

What's Armory's RAM usage? I think you are confusing RAM used by the process and in use memory pages. The OS won't shy away from filling that up when a lot of access is performed on mmap'ed files, which will happen a lot during a DB scan. That doesn't mean the RAM is in use, it means the OS is chugging unused RAM to shuffle file data in and out of it. If a process was to ask for more RAM it would get priority over this memory.

The OS has no reason to empty this memory once Armory is done scanning. For all it knows, Armory just asked for intensive access to this data, so the OS expects it will again. Unless other processes start asking for more RAM or Armory is closed, the OS will keep these unused pages filled with the DB's mmap'ed files.

I think you are correct. It's probably not a memory leak, ArmoryQt itself only uses 300M, on top of bitcoind's 500M. However it's still scary to see so much memory being mmap'd, rarely have I seen this before.

Thanks for pointing that out.

If you restart Armory it shouldn't be mmap'ing as much memory. Next version will be a lot tamer on that front, and I also may just close and reopen the DB just to flush out the mmap data after the scan is over. For now you'll have to deal with the scary numbers =P