Control: tag -1 pending
On Tue, Apr 22, 2014 at 11:23:24AM +0200, Petter Reinholdtsen wrote:
>
> Package: python-apt
> Version: 0.8.8.2
> Severity: important
>
> Since I wrote the isenkram package, it have been plagued with a nasty
> resourse leak. It leak memory and file descriptors every time
Hi everyone!
On Wed, Apr 23, 2014 at 10:09:15AM +0200, Michael Vogt wrote:
> On Tue, Apr 22, 2014 at 11:23:24AM +0200, Petter Reinholdtsen wrote:
> > Package: python-apt
> > Version: 0.8.8.2
> > Severity: important
>
> Thanks for your bugreport.
>
> > Since I wrote the isenkram package, it have
Hi,
What is the current state of this in Jessie?
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
[Michael Vogt]
> Thanks for this demo, I can reproduce the issue with it. However, if
> I change it a little bit and force the python garbage collector
> there seems to be no leak (or a small memory leak but no fd leak).
Aha. Calling gc.collect() after I am done using the apt cache in the
isenkra
On Tue, Apr 22, 2014 at 11:23:24AM +0200, Petter Reinholdtsen wrote:
> Package: python-apt
> Version: 0.8.8.2
> Severity: important
Thanks for your bugreport.
> Since I wrote the isenkram package, it have been plagued with a nasty
> resourse leak. It leak memory and file descriptors every time
On Tue, Apr 22, 2014 at 11:23:24AM +0200, Petter Reinholdtsen wrote:
>
> Package: python-apt
> Version: 0.8.8.2
> Severity: important
>
> Since I wrote the isenkram package, it have been plagued with a nasty
> resourse leak. It leak memory and file descriptors every time some
> hardware is inser
Hm, look like this issue is and old and known problem, at least to
some. I found it mentioned in
http://stackoverflow.com/questions/17624114/how-to-diagnose-potential-memory-leak-in-python-program
>
from 2013-07-12.
To me, the issue seem similar to
https://bugs.debian.org/cgi-bin/bugreport.cgi?b
Package: python-apt
Version: 0.8.8.2
Severity: important
Since I wrote the isenkram package, it have been plagued with a nasty
resourse leak. It leak memory and file descriptors every time some
hardware is inserted. The amount of leaked memory varies, but seem to
be 30-40 MiB every time. The a
8 matches
Mail list logo