Subversion blows


The amazing thing here is that manual pool management doesn't actually fix everything. While it reduces the amount of memory leaked by at least an order of magnitude, it doesn't eliminate it.
If memory is a scarce resource, (like on a server I run) the only viable option is to abandon the libsvn bindings and go back to backticked svn(1) calls.

I've recently visited the bugtracker of apache subversion (yes, it's an official apache project these days, the apache foundation must be proud) to see if they had more information on this issue. (or the others) None of them had open bugs, but other bugs, one of them named "perl bindings segfault very often", didn't sound encouraging.
I looked through the related code some, but there's more arcane perl in there than I'm willing to bother learning.

Add Comment

All fields are optional. Your email address will not be publicly displayed.
HTML-Tags will be converted to Entities.
Standard emoticons like :-) and ;-) are converted to images.