Memory Leak in walletlock - Threads spawned and never killed #639

issue abieganski opened this issue on November 17, 2011
  1. abieganski commented at 10:28 AM on November 17, 2011: none

    After calling walletlock on the Windows version of bitcoin daemon many times (via command line or json-rpc), this error appears in the debug.log:

    N5boost16exception_detail10clone_implINS0_19error_info_injectorINS_21thread_resource_errorEEEEE boost::thread_resource_error

    I checked the number of threads belonging to the bitcoind.exe process, and every time walletlock is called, thread count increases by one. Those thread do not die and eventually the no of threads limit is breached and the daemon crashes.

  2. jordanmack cross-referenced this on Nov 18, 2011 from issue Intermittant crash in bitcoin-qt.exe 0.5.0 rc5 when using RPC commands by jordanmack
  3. laanwj cross-referenced this on Feb 11, 2012 from issue bitcoin-qt 0.5.2 crash after extended run with p2pool by rm44377
  4. sipa cross-referenced this on Feb 11, 2012 from issue Fix wallet locking locking by sipa
  5. TheBlueMatt commented at 6:58 PM on February 16, 2012: contributor

    Can someone who was able to duplicate this issue test got HEAD and see if the problem persists?

  6. sipa commented at 5:58 PM on February 19, 2012: member

    I verified the problem is fixed, though a confirmation from the original submitter would be nice.

  7. gavinandresen closed this on Feb 27, 2012

  8. unsystemizer cross-referenced this on Aug 27, 2015 from issue boost::thread_resource_error: Resource temporarily unavailable on Rasbpian Jessie by unsystemizer
  9. ptschip referenced this in commit 788f3e5575 on Jun 6, 2017
  10. kallewoof referenced this in commit 4858d36163 on Oct 4, 2019
  11. KolbyML referenced this in commit bc86927231 on Sep 4, 2020
  12. rajarshimaitra referenced this in commit 94752bfdc5 on Aug 5, 2021
  13. bitcoin locked this on Sep 8, 2021

github-metadata-mirror

This is a metadata mirror of the GitHub repository bitcoin/bitcoin. This site is not affiliated with GitHub. Content is generated from a GitHub metadata backup.
generated: 2026-05-20 06:56 UTC