On Tuesday 28 Jun 2005 12:44, Michael Vogt wrote: > I would like to know if this memory leak is still there with the > latest version of apt-proxy (currently 1.9.31).
It seemed to have gone away but came back every now and again for me. I have found one way to reproduce it, and I think that it is not a leak as such, but a problem where apt_pkg grabs large amounts of memory (about 12Mb per instance) if sources.list is empty or there are no valid Packages files available. I've extracted this into a separate script (attached) that demonstrates the problem. Since it does not make sense to load the packages database if there are no packages files I have also added a test to my development apt-proxy that skips loading the cache if there are no packages files available. This should fix the problem in apt-proxy itself. Chris
test_memleak.py
Description: application/python
