Edwin Groothuis wrote:
On Sun, Nov 28, 2004 at 07:38:06PM -0500, Chuck Swiger wrote:
439 ldap 200 149M 6128K kserel 0:07 0.00% 0.00% slapd
I know that the actually used memory size is the 6MB figure above, but
why does it allocate almost 150MB? Is it normal?
This sounds like a
Running 2.2.18, mine gets up to 600+ MB before crashing with an unable to
ch_malloc error. Have had this with several of the 2.2.x releases, went
back to 2.2.17 and it's running fine again.
I think this is more of something for the openldap-users list.
-Mike
On Thu, 25 Nov 2004, Ivan Voras
Ivan Voras wrote:
Edwin Groothuis wrote:
On Sun, Nov 28, 2004 at 07:38:06PM -0500, Chuck Swiger wrote:
[ ... ]
I know that the actually used memory size is the 6MB figure above,
but why does it allocate almost 150MB? Is it normal?
This sounds like a classic example of a memory leak.
Had the same
On Mon, 2004-Nov-29 10:54:43 -0500, Chuck Swiger wrote:
5-base# leaks 78
Process 78: 284 nodes malloced for 38 KB
Process 78: 232 leaks for 5568 total leaked bytes.
Leak: 0x001018f0 size=32
0x 0x0002 0x0002 0x0011
0x0010 0x 0x001018b0 0x
Ivan Voras wrote:
After a few days of mostly test load, top reports that the slapd process
(OpenLDAP server) is huge:
439 ldap 200 149M 6128K kserel 0:07 0.00% 0.00% slapd
I know that the actually used memory size is the 6MB figure above, but
why does it allocate almost 150MB?
On Sun, Nov 28, 2004 at 07:38:06PM -0500, Chuck Swiger wrote:
Ivan Voras wrote:
After a few days of mostly test load, top reports that the slapd process
(OpenLDAP server) is huge:
439 ldap 200 149M 6128K kserel 0:07 0.00% 0.00% slapd
I know that the actually used memory
Hi.
On Thu, Nov 25, 2004 at 05:03:48PM +0100, Ivan Voras wrote:
After a few days of mostly test load, top reports that the slapd process
(OpenLDAP server) is huge:
439 ldap 200 149M 6128K kserel 0:07 0.00% 0.00% slapd
I know that the actually used memory size is the 6MB
