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

issue abieganski opened this issue on November 17, 2011

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.
TheBlueMatt commented at 6:58 PM on February 16, 2012: member

Can someone who was able to duplicate this issue test got HEAD and see if the problem persists?
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.
gavinandresen closed this on Feb 27, 2012
ptschip referenced this in commit 788f3e5575 on Jun 6, 2017
kallewoof referenced this in commit 4858d36163 on Oct 4, 2019
KolbyML referenced this in commit bc86927231 on Sep 4, 2020
rajarshimaitra referenced this in commit 94752bfdc5 on Aug 5, 2021
MarcoFalke locked this on Sep 8, 2021

Contributors

Labels