Wombat will get into this memory eating loop every time I open the meeting dialog, so I do not think it is ldap related. Is there anything I can do to help speed up the resolution of this bug? Is there some kind of tracing that I can set ? Ron On Thu, 2003-04-17 at 23:23, Ron Smits wrote: > running evolution 1.3.2 with openldap 2.0.9 trying to schedule a meeting > will make wombat go mad. It will eat all memory and swap. > > Attached is a compressed strace of the wombat process > > Ron
Attachment:
signature.asc
Description: This is a digitally signed message part