0.14.0 Runtime Error/Out of memory #9969

1. 
   hoke81 commented at 2:54 pm on March 10, 2017: none

   Updated to 0.14 on my netbook, because it was promised to be faster and less resource consuming in some ways. It runs for from 15 minutes only to some hours until a Runtime Error occurs. Last entry in debug.log is “Error: Out of memory. Terminating.”, before nothing special. I have installed it on an external HD, because no internal one had over 100GB free, 0.13.2 was running fine with that and is again now.

   Machine specs:

   • OS: Windows 10 home
   • CPU: N570 1,66 GHz
   • RAM: 2GB
   • Disk size: 149GB
   • Disk Type (HD/SDD): USB-HDD
2. laanwj added the label Resource usage on Mar 13, 2017
3. 
   alafax commented at 6:53 pm on March 13, 2017: none

   I have same issue on 0.14 BTC wallet,Runtime errors during sync - “Error: Out of memory. Terminating.”

   I had to revert on 0.13.2 which works perfectly.

   Machine specs:

   OS - Windows 7 Professional 32bit CPU - Intel Core Quad Q8200 2.33GHz RAM - 4GB Disk size - 640GB HD

4. 
   chandlerchao commented at 8:36 pm on March 15, 2017: none

   I have noticed this issue as well. Even with setting dbcache, maxmempool, and maxconnections, 14.0 still seems to crash with an “Out of memory” error while syncing the blockchain.

   My bitcoind is compiled from source. I’m going to attempt to compile 13.2 and see if that shows the same problem.

   Machine specs:

   • OS - Ubuntu 12.04
   • CPU - ARM
   • RAM - 2G
   • Disk size: 160G
   • Disk Type: USB-HDD
5. 
   alafax commented at 8:56 pm on March 15, 2017: none

   I think that 0.14 wallet has serious memory leaking problem.

   With dbcache set on 300MB on 0.13.2 I had no problems(4GB RAM) - (but setting on 500MB resulted in Out of memory after 12 or more hours of continuos working).

   Users with 2GB RAM should try to set dbcache on 150MB or less.

6. 
   laanwj commented at 10:18 am on March 16, 2017: member

   I think that 0.14 wallet has serious memory leaking problem.

   What makes you suspect the wallet?

7. 
   chandlerchao commented at 12:09 pm on March 16, 2017: none

   I don’t believe it is the wallet that is causing the memory leak. I compile with the wallet disabled. At this point 13.2 is running without the memory issue with all default settings.
8. 
   sipa commented at 7:51 pm on March 16, 2017: member

   @alafax As far as I know, Bitcoin Core has no memory leaks at all (which means it doesn’t lose track of allocated memory, making it accumulate over time). However, it’s certainly the case that 0.14 has slightly higher default memory usage than 0.13, and during IBD a higher peak memory usage while flushing. We’re looking into it, and for now, you can avoid the issue wiht just lower -dbcache and -maxmempool settings.
9. 
   alafax commented at 0:28 am on March 17, 2017: none

   @chandlerchao I agree for 0.13.2. It works OK on default settings (dbcache 300MB).During 24h test it did not crash. But 0.14 crash every time after 15-25 minutes, with same settings as 0.13.2. I monitored memory usage and did not see that 0.14 has bigger memory peaks than 0.13.2.Though it is definetly memory handling problem and if it is not memory leakage than I suspect IBD pushed weaker machines over their limits.
10. 
    mecampbellsoup commented at 1:18 pm on March 21, 2017: none

    Also experienced a crash with the message “Out of memory. Terminating.” I took @sipa suggestion and lowered dbcache from 5GB to 2GB and maxmempool from 300 (the default) to 200; have not experienced another crash since restarting with those changes.
11. 
    ghost commented at 7:29 pm on April 30, 2017: none

    Bitcoin Core Version 0.14, Bitcoin-qt terminated here too due to ’error, out of memory’ in the debug.log. Ubuntu 14.04 - 32 bit, 1g mem + 1 g swap. Never had that with 0.13 or earlier versions.
12. 
    sipa commented at 7:30 pm on April 30, 2017: member

    @coinsmith There is a known memory usage increase in 0.14.0, please upgrade to 0.14.1 which fixes it.
13. 
    ghost commented at 7:31 pm on April 30, 2017: none

    Will do.
14. 
    Leviathn commented at 1:01 pm on September 5, 2017: none

    This appears closeable.
15. fanquake closed this on Sep 5, 2017

    ---

16. DrahtBot locked this on Sep 8, 2021

Contributors
hoke81 alafax chandlerchao laanwj sipa mecampbellsoup ghost Leviathn

Labels
Resource usage