Opened 17 years ago
Closed 17 years ago
#6581 closed defect (fixed)
[PATCH] memory leak in svn_fs.py
Reported by: | Owned by: | Jeroen Ruigrok van der Werven | |
---|---|---|---|
Priority: | high | Milestone: | 0.11 |
Component: | version control | Version: | devel |
Severity: | normal | Keywords: | |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description (last modified by )
There's a reference cycle between SubversionRepository and RealSubversionAuthorizer that isn't collectable because of the __del__
method on SubversionRepository. The attached patch fixes the problem.
Attachments (1)
Change History (5)
by , 17 years ago
Attachment: | svn_fs.diff added |
---|
comment:1 by , 17 years ago
Description: | modified (diff) |
---|---|
Milestone: | → 0.11 |
Priority: | normal → high |
comment:2 by , 17 years ago
comment:3 by , 17 years ago
Owner: | changed from | to
---|
Yeah, I was about to test it… I just have to update now instead of patching the file, so it's not really getting in the way ;-)
I'll report back my findings.
comment:4 by , 17 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
There are apparently no memory savings (no visible leak either) with or without, only high but stable memory usage, as usual.
When the repository gets explicitly close()
d, this effectively frees the svn objects. The repository object itself might be leaked without the patch, but the impact of this is quite minor and I don't thinkg it explains the high memory usage we're seeing.
But it's better to avoid that (probably very minor) leak anyway, so I'm closing the issue.
Anyway, for 0.12, the whole SvnAuthorizer stuff could be easily adapted to the security framework (no user visible changes, only an implementation detail).
Committed in r6385.
Only just saw that you changed the ticket Christian, sorry, was not trying to get in the way.