[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: (ITS#3609) ch_malloc of 8388608 bytes failed

Thanks for your comments.  The threads setting is at 4.

I guess I'll stick with bdb, but switch to 4.2.52 (with patches).

On 3/30/2005 5:53 PM, Howard Chu wrote:
> I do not recommend reducing the size of the searchstack. Instead, 
> decrease the maximum number of threads from the default of 16 to 
> something much lower. The fact that your backtrace only shows one thread 
> running is probably just an artifact of the debugging environment not 
> being able to get full status information after a fatal exception. This 
> frequently happens if the gdb binary was compiled against a different 
> version of libc headers than you're currently running under. At any 
> rate, the lack of information about other threads is not a reliable 
> indicator of the program's actual thread state.
> The back-ldbm backend has lower memory requirements but is not 
> recommended for any deployments because it has locking and stability 
> issues.
> bsmith@sudleyplace.com wrote:
>> No sooner had I configured <slapd.conf> as described below and then 
>> tested it exactly as before, did it crash again.  This time I ran
>> thread apply all bt full
>> but apparently there was only one thread running.  As before, I put 
>> all this onto my web site at
>> http://www.sudleyplace.com/backtrace.html
>> Any suggestions you can make as to different values for these 
>> parameters or other parameters, please let me know.  Also, I'd be 
>> willing to try a less memory-hungry backend if you think that'll help.

Bob Smith - bsmith@sudleyplace.com - http://www.sudleyplace.com
a.k.a.      bsmith@qualitas.com    - http://www.qualitas.com