8:38 p.m.
Hi all,
I found an interesting post about error handling and how to avoid such
leaks - please check:
https://cosmicpercolator.com/2016/01/13/exception-leaks-in-python-2-and-3/
Nir
9:27 a.m.
On Sun, Sep 04, 2016 at 08:38:30PM +0300, Nir Soffer wrote:
Hi all,
I found an interesting post about error handling and how to avoid such
leaks - please check:
https://cosmicpercolator.com/2016/01/13/exception-leaks-in-python-2-and-3/
Nir
Interesting. Afrer enough time, we would have one traceback object per
live thread, and we may have plenty of such object prior to garbage
collection.
Have you tried if running gc.collect() clears these stale traceback
objects you've seen?
9:48 a.m.
On Mon, Sep 5, 2016 at 9:27 AM, Dan Kenigsberg <danken(a)redhat.com> wrote:
On Sun, Sep 04, 2016 at 08:38:30PM +0300, Nir Soffer wrote:
> Hi all,
>
> I found an interesting post about error handling and how to avoid such
> leaks - please check:
> https://cosmicpercolator.com/2016/01/13/exception-leaks-in-python-2-and-3/
>
> Nir
Interesting. Afrer enough time, we would have one traceback object per
live thread, and we may have plenty of such object prior to garbage
collection.
Have you tried if running gc.collect() clears these stale traceback
objects you've seen?
I have seen living tracebacks in a system doing gc.collect once per
minute (health monitor enabled), but I did not monitor yet the instances,
not sure how much time each instance was living.
I also did not check how much memory was reference by each traceback,
this needs more time to research.
Regardless I think we should start to be more careful about these.
Nir
2999
days inactive
3000
days old
2 comments
2 participants
participants (2)
-
Dan Kenigsberg -
Nir Soffer