Quote from: goatpig on December 02, 2016, 09:14:28 AM

1) Please don't hijack somebody else's thread, create your own and post your log files.

People providing data about about the same problem isn't a hijack, it's an attempt to help find a solution to a problem.

Quote from: goatpig on December 02, 2016, 09:14:28 AM

2) There is a difference between allocated memory (malloc) and mapped files (mmap). The usage figures show you total RAM load, but the distinction is significant: allocated memory belongs to the process while mapped files boils down to hinting the OS that you want these files cached in RAM for faster access. Mapped memory does not prevent new allocations, it simply uses otherwise free resources to speed up I/O.

You are correct, I misread it.. it hammers the machine so hard it -acts- like it's completely out of ram and into swap.

Quote from: goatpig on December 02, 2016, 09:14:28 AM

3) This is an open source project, feel free to submit code if you have a better solution, or at least participate to the testing phases and provide constructive feedback and bug tracking.

True.

I hope you understand peoples frustration here...a product, free or not, they've been using, has become, for whatever reason, impossible to use, monopolizing their machines, and most importantly, holding their BTC hostage.

Speaking of which, after another over-night run, the client finally appears happy and caught up, except all the wallets have zero balance. Rescan gave zero change.

help?