The client (bitcoin-qt 0.9.2.1) is connected, up to date and ~307k transactions are processed.
Cpu and hdd wise it is idling.
Although it occupies a huge piece of the ram! Its at ~700 MiB! Its there right after the start. (So it didnt slowly climb.)
For doing nothing thats way to much.
Virtual memory or actual resident memory? What platform/architecture?
Vm is even more: ~1.6 GiB but that is fine, I think. The ~700 MiB are rss. Linux amd64 (gentoo, if that matters).
How long after startup are you seeing that memory usage? My bitcoind (also gentoo/amd64, no qt) takes many hundred MB during startup while it's verifying the DB, then it drops down to ~180MB. It takes about ~500MB when it's been running for a several days.
So initial memory usage (during startup) is quite high, and memory usage gradually builds up high, but I'm not seeing persistent memory usage from the start.
I start the application, it takes about 25s until the main window appears and then the memory is already filled. (According to top and iotop bitcoin-qt is doing "nothing".) The memory is not freed after days of doing "nothing", just let it sit in the background. (Just the usual p2p work.)
@m4rkusxxl Does this also happen if you start with -disablewallet?
Memory usage is perhaps a little less but not significant.
mine (bitcoind w/ wallet disabled) was using 8GB of resident memory earlier, w/ 900 connections. data buffers? storing txes or blocks for peers that arent there anymore?
For me the rss is used right from the beginning. Its not climbing over time. (At least not that I am aware of.)
I am currently running into this issue on FreeBSD 9.2 64-bit. I have the connections limited to just 5, but the bitcoind process is using up all the system's RAM. It's currently at 1.4 GB and growing:
bitcoinuser 1387 3.0 55.4 1388540 568276 ?? INLs 29Jul14 826:14.22 /usr/local/bin/bitcoind -conf=/usr/local/etc/bitcoin.conf -datadir=/var/db/bitcoin -noupnp -daemon -pid=/var/db/bitcoin/bitcoind.pid
The system has only 2GB of RAM.
CPU: 0.0% user, 15.6% nice, 4.3% system, 0.4% interrupt, 79.7% idle
Mem: 584M Active, 152M Inact, 199M Wired, 23M Cache, 110M Buf, 13M Free
Swap: 5120M Total, 933M Used, 4186M Free, 18% Inuse, 3720K In
Here are some logs and process information http://venus.morante.net/downloads/unibia/other/debug.log.gz http://venus.morante.net/downloads/unibia/other/bitcoind_info
I haven't restated the process yet, so if there is anything else I could collect I would be glad to.
Nothing obviously strange going on in that log or process information, that I noticed at least.
I saved this as an image, so it'd be readable (formatting etc)
We are having the same problem here. we are having bitcoin running at 1.4 GB on windows server 2012
machine 1 is now at 2272 (+139MB), machine 2 is at 1670 (+771MB).. time is 1225pm UTC.
OK, a new block hit at around 1231pm UTC. Machine 1 went from 2270 to 2320MB, machine 2 went from 1674 to 1861MB. So machine 1 is apparently clearing a bit of RAM between blocks, but 2 is still gaining, possibly from more orphan transactions?
This was block 31899, 925KB w/ 1313 transactions.
(ed: fixed machine 1 total before block)
2323 and 1935MB respectively now, after 5 more blocks. 2nd one is still going up a bit. 476 and 423 connections respectively. Probably has something to do with buffering something in memory to each of those connections & not clearing ??
So then people may see more memory usage than normal if Mothership.Aiur is still going around opening 30 or 40 connections to everyone