Ravencoin
Ravencoin copied to clipboard
WIN;QT Extremely high Commit memory size (Gigabytes leaked)
Raven Core version v2.4.0.0-ed857ac (64-bit), Win 10
After running as a node for maybe a week (less than ten days at least), Commit memory size had ballooned to over six gigabyte; Working set hovered around 0.4GiB, same as the amount used when starting it.
Transactions page active. Pretty much always run minimized, interrupted a few times/day by user interactions "Copy amount" context menu interaction for incoming transactions.
Since this behavior is unique to Raven Core, compared to f.ex. Vertcoin Core, it's without question a Raven-specific issue. My initial suspicion is the binance price integration, since that's the most obvious difference. I missed to check the HANDLE count on the process before exiting, but I wouldn't rule out HANDLE leaks, though it'd have to be a LOT of handle's to leak that amount of memory.
@tamlin-mike Thanks for bring this to our attention. I will look into this and see what I can find out.
Follow-up info: After approx 60h runtime: 320MiB working set, around 2GiB Committed. Handle count is just over 1k, most to the chain db files, so that's not the problem. For memory profiling, I'd suggest initial focus on the binance integration.
++luck;
cant reproduce on 4.3.2.1
I have the same issue in Budapest. I habe 64Gb in the Pi and on the first two days everything was fine but then... well in about 30 minutes as I observed in the "top" the CPU usage went a bit down from 99.x% to 50% or so but the memory started to go up up and up till 100% and at this point the Pi killed my process. How big of a memory do I need to use or can I limit the usage of the process so it keeps the process alive? :/