You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
gc.DEBUG_STATS reports invalid "elapsed" times #46719
If gc.set_debug(gc.DEBUG_STATS) is enabled, collection will report
elapsed time as it progresses through collection. However, the
reporting code clobbers the value it uses to compute the elapsed time,
so the value alternates between an almost correct valid and a completely
incorrect value.
The original code is pretty icky. I'm attaching a patch that improves
it, IMO. Before the elapsed time was only shown if garbage was found.
I think it should always be shown if DEBUG_STATS is set.
Activity
exarkun commentedon Mar 23, 2008
If gc.set_debug(gc.DEBUG_STATS) is enabled, collection will report
elapsed time as it progresses through collection. However, the
reporting code clobbers the value it uses to compute the elapsed time,
so the value alternates between an almost correct valid and a completely
incorrect value.
nascheme commentedon Mar 25, 2008
The original code is pretty icky. I'm attaching a patch that improves
it, IMO. Before the elapsed time was only shown if garbage was found.
I think it should always be shown if DEBUG_STATS is set.
pitrou commentedon Dec 17, 2008
Fixed in r67832, thanks!