From owner-freebsd-questions Fri Mar 3 13:17: 0 2000 Delivered-To: freebsd-questions@freebsd.org Received: from ns1.webgator.com (ns1.webgator.com [208.218.82.136]) by hub.freebsd.org (Postfix) with ESMTP id 3EA4A37B6AB for ; Fri, 3 Mar 2000 13:16:51 -0800 (PST) (envelope-from dhummel@rtheory.com) Received: from rtheory.com (localhost [127.0.0.1]) by ns1.webgator.com (8.9.3/8.9.3) with ESMTP id QAA24255; Fri, 3 Mar 2000 16:16:44 -0500 (EST) (envelope-from dhummel@rtheory.com) Message-ID: <38C02BBC.7AD9EF23@rtheory.com> Date: Fri, 03 Mar 2000 16:16:44 -0500 From: Dave Hummel X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.0.36 i386) X-Accept-Language: en MIME-Version: 1.0 To: "FreeBSD-questions@FreeBSD.ORG" Cc: ulmo@earthling.net Subject: Help! My treads are leaking: Openldap References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I've hit a brick wall with getting openldap to work properly. Here's an extract from my mail to the openldap mailing list: Systems are now FreeBSD 3.4-stable, cvsup'd and compiled Feb 22, using FreeBSD uthreads. (db-2.7.7, openldap-1.2.9 both compiled from scratch (not ports) following directions/readmes found at openldap/sleepycat). Previous compile was Feb 14. I am unhappy to say the the problem has not relented even slightly. I tried two different boxes, and the result is the same. Again, configuring --without-threads causes slapd to behave properly. The problem in question is that slapd, compiled with native threads will grow with each ldap operation until all memory is exhausted. Limiting cachesize has no effect. I have no problems whatsoever when compiled without threads. I have tried FreeBSD 3.3 stable/Openldap 1.2.8 and FreeBSD 3.4 stable/Openldap 1.2.9 with the same results. I have tried the native FreeBSD db, as well as Sleepycat's latest version. I have also tried this on several boxes, all with recently cvsup'd code with a variety of compile options. I have tried building from the port, and building by hand. Every time the result is the same. It would appear that there is definitely some leakage with the thread routines. Could somebody give me a few pointers on how to track down the cause of this leakage? This is very annoying, and I know of several other people who have been struggling with this problem for a long time. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message