Memory leak with after_cancel() in Tkinter
I'm experiencing this myself with an event driven simulator that makes
*heavy* use of after() and after_cancel().
I've seen references to this bug.
Has it been fixed in Python 2.2.2?
|All times are GMT. The time now is 10:30 PM.|
Powered by vBulletin®. Copyright ©2000 - 2014, vBulletin Solutions, Inc.
SEO by vBSEO ©2010, Crawlability, Inc.