<p>It seems to be an <a href="http://www.boost.org/doc/libs/1_34_0/doc/html/boost/thread_resource_error.html" rel="nofollow">error from the Boost library</a> that is thrown "thread-related resources cannot be acquired". You probably should contact the dev team about this error, from your description it appears to be a memory leak.</p>

CC BY-SA 3.0
2011-11-16T16:51:54.743Z
It seems like the problem is the walletlock method of the API.
Whenever it is called, a new thread is created and it doesn't die. Do you know where I can report this bug?
bitboy9999
CC BY-SA 3.0
2011-11-16T18:39:57.520Z
I`d submit it either here https://bitcointalk.org/index.php?board=4.0 or here https://github.com/bitcoin/bitcoin/issues or email the devs. Probably the second option is the best.
ThePiachu
CC BY-SA 3.0
2011-11-16T16:22:07.320Z
2011-11-16T16:22:07.320Z
ThePiachu
<p>I am getting this error in the debug.log of bitcoind:</p>

<p>EXCEPTION: N5boost16exception_detail10clone_implINS0_19error_info_injectorINS_21thread_resource_errorEEEEE<br>
boost::thread_resource_error </p>

<p>It happens every 2 to 4 hours, and I need to restart bitcoind.</p>

<p>What I do is I request recent transactions every 2 seconds, via json-rpc.</p>

<p>Does anybody else got this error? Is there a way of avoiding this error?</p>

<p><strong>UPDATE:</strong></p>

<p>I actually managed to figure out it is related to calling <em>walletlock</em>. Whenever <em>walletlock</em> is called (via json-rpc or command line, doesn't matter), a new thread is spawned and it doesn't die. Looks like a bug.</p>

CC BY-SA 3.0
2011-11-16T16:47:47.343Z
What is the exact RPC call you issue? `listtransactions`?
David Schwartz
CC BY-SA 3.0
2011-11-16T17:32:33.663Z
I actually managed to figure out it related to calling walletlock. Whenever walletlock is called (via json-rpc or command line, doesn't matter), a new thread is spawned and it doesn't die. Looks like a bug.
bitboy9999
<bitcoind>
boost::thread_resource_error
bitboy9999
# boost::thread_resource_error

(Asked by: username_0 on 2011-11-16)

I am getting this error in the debug.log of bitcoind:

EXCEPTION: N5boost16exception\_detail10clone\_implINS0\_19error\_info\_injectorINS\_21thread\_resource\_errorEEEEE  
boost::thread\_resource\_error

It happens every 2 to 4 hours, and I need to restart bitcoind.

What I do is I request recent transactions every 2 seconds, via json-rpc.

Does anybody else got this error? Is there a way of avoiding this error?

**UPDATE:**

I actually managed to figure out it is related to calling *walletlock*. Whenever *walletlock* is called (via json-rpc or command line, doesn't matter), a new thread is spawned and it doesn't die. Looks like a bug.

**Tags:** bitcoind

> **Comments:**
> **username_1**: What is the exact RPC call you issue? `listtransactions`?  
> **username_0**: I actually managed to figure out it related to calling walletlock. Whenever walletlock is called (via json-rpc or command line, doesn't matter), a new thread is spawned and it doesn't die. Looks like a bug.  

---

## 1 answers

### Answer by username_2 on 2011-11-16. Score: 1

It seems to be an [error from the Boost library](http://www.boost.org/doc/libs/1_34_0/doc/html/boost/thread_resource_error.html) that is thrown "thread-related resources cannot be acquired". You probably should contact the dev team about this error, from your description it appears to be a memory leak.

> **Comments:**
> **username_0**: It seems like the problem is the walletlock method of the API. Whenever it is called, a new thread is created and it doesn't die. Do you know where I can report this bug?  
> **username_2**: I`d submit it either here https://bitcointalk.org/index.php?board=4.0 or here https://github.com/bitcoin/bitcoin/issues or email the devs. Probably the second option is the best.  

---

