Eric Covener <> changed:

           What    |Removed                     |Added
             Status|NEW                         |NEEDINFO

--- Comment #2 from Eric Covener <> ---
2.4.32 is around the corner and does have an LDAP concurrency fix, but usually
it leads to high CPU and not a crash.  But, it is probably worth revisiting
this if you can.

If it doesn't pan out -- could you try to run your scenario under
valgrind to potentially make it fail earlier?  and/or grab "trace8" output
leading to the crash?

You are receiving this mail because:
You are the assignee for the bug.
To unsubscribe, e-mail:
For additional commands, e-mail:

Reply via email to