What does it mean: EXCEPTION: 11DbException

[dmiceman]

Hello.

Two days ago I have start to receive message boxes from bitcoin client telling me:

EXCEPTION: 11DbException       
Db::get: Cannot allocate memory       
bitcoin in ProcessMessage()     

What does it mean? Is that only me? What to do with it?

Version: 0.3.21 on arch linux. No activity with client in a weeks - it just stay here and accept blockchain.

[1715271088]

1715271088

[1715271088]

1715271088

[bittrader]

I don't suppose your box is actually getting low on memory while the client is running?

Or maybe just low on disk space in the partition where the database files are stored.

[dmiceman]

No. I have around 2.5 Gb of free memory and around 500 Gb of free disk space.

[netrin]

EXCEPTION: 11DbException       
Db::get: Cannot allocate memory       
bitcoin in ProcessMessage()     

I am seeing this error code in version 0.3.23 Ubuntu 11.04, except not a memory issue.

Code:

EXCEPTION: 11DbException
Db::open: Invalid argument
bitcoin in AppInit()

[PandaMiner]

I am getting a similar error in my Unbuntu Live USB (back up wallet).

Code:

EXCEPTION: 11DbException       
Db::put: Cannot allocate memory       
bitcoin in ProcessMessage() 

Only that it's PUT.  It is not downloading any more new blocks from the chain. It's stuck at 134229 since I got that error.

Would also like to mention, that I tried to copy the wallet.dat file to a third installation to see if one could really steal my coins if they had my dat file. Well, on the 3rd machine, it said "WARNING: Balance may not be the same" or similar. 

Now the linux says the same thing.

[molecular]

sorry to necropost, but how much memory does bitcoin need nowadays?

I'm running into the same problem:

Code:

************************
EXCEPTION: 11DbException
Db::get: Cannot allocate memory
bitcoin in Runaway exception

bitcoin: /usr/include/boost/thread/pthread/mutex.hpp:50: void boost::mutex::lock(): Assertion `!pthread_mutex_lock(&m)' failed.

I have 1.3GB free (no swap drive due to now harddrive being present, not going down the "swap to nfs" route again) and right before the exception there's still 1.2GB free.

Is there such a large chunk of memory being allocated in one go?