Opened 9 years ago

Last modified 9 years ago

#3417 new defect

Leaking LDAP connections

Reported by: memfis Owned by: eblot
Priority: normal Component: LdapPlugin
Severity: major Keywords:
Cc: Trac Release: 0.10


LdapPlugin doesn't seem to close the LDAP connections it makes. With every hit to a Trac page the system connection count grows. I haven't seen a single call to close() in LdapPlugin's source, why is that?

Attachments (0)

Change History (2)

comment:1 Changed 9 years ago by eblot

  • Priority changed from highest to normal
  • Severity changed from blocker to major

LDAP connections objects are dereferenced, which should close the connection when the object is garbage-collected.

The code needs some serious clean up though.

BTW, please be fair with priority and severity levels. You won't get better answers if you set levels unrelated to the actual issue.

comment:2 Changed 9 years ago by memfis

Well, reality shows that they aren't. As far as I checked, the python ldap library doesn't have any destructors defined for any of its objects, so I don't see have the connection is supposed to be closed when they get dereferenced.

Now with the priority and severity levels. I don't know about you, but a problem that causes severe connection leaks and therefore makes a piece of software useless is a blocker to me.

Add Comment

Modify Ticket

as new The owner will remain eblot.

E-mail address and user name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.