This repository has been archived by the owner on Nov 23, 2017. It is now read-only.

Do we need to call gc.collect() occasionally through the event loop? #42

Closed

GoogleCodeExporter opened this issue Apr 10, 2015 · 5 comments

Labels

auto-migrated Priority-Low Type-Defect

GoogleCodeExporter commented Apr 10, 2015

I closed issue 41 as fixed, but there's one missing piece: abandoned tracebacks 
only get printed when the Future is garbage-collected.  If nothing else is 
going on this may take a while.  Perhaps we should have some heuristic in 
_run_once() that occasionally calls gc.collect()?

Every time _run_once() is called is probably too often -- maybe we should call 
it at most once a second?

Original issue reported on code.google.com by gvanrossum@gmail.com on 3 May 2013 at 10:20

Merged into: Reference cycle in _TracebackLogger and bug in _TracebackLogger.__del__() #155

The text was updated successfully, but these errors were encountered:

GoogleCodeExporter added auto-migrated Type-Defect Priority-Low labels

GoogleCodeExporter closed this as completed

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.