Aha! Greg, you've given me the clue I needed. I never thought to look into
how to trigger a garbage collect. I assumed (incorrectly) that it was
something hidden away from users and that I couldn't do anything about it.
Researching more, I see that I can indeed trigger a garbage collect myse
I've been trying to figure out how to trigger the garbage collect. Do you have
any clues Greg? This is EXACTLY what's happening.
-Original Message-
From: Tkinter-discuss
On Behalf Of Greg
Ewing
Sent: Sunday, December 15, 2019 5:39 PM
To: tkinter-discuss@python.org
Subject: Re: [Tkin
On 16/12/19 11:18 am, Mike Barnett wrote:
There are no tkinter calls made from any thread other than the main thread.
It looks like some tkinter objects are becoming part of garbage
cycles, and getting collected by whatever thread happens to be
running when the cyclic gc kicks in.
Seems to me
That's how it looks but I can assure you that the thread are not running
the mainloop. There are no tkinter calls made from any thread other than the
main thread.
-Original Message-
From: Tkinter-discuss
On Behalf Of
Michael Lange
Sent: Sunday, December 15, 2019 5:16 PM
To: tki
Hi,
On Sun, 15 Dec 2019 18:29:18 +
Mike Barnett wrote:
> I've been fighting this error for a couple of years now and just when I
> think I've got it understood and "Fixed", it bites me again.
>
>
>
> Here's the error:
>
>
>
> Exception ignored in:
>
> Traceback (most recent call last):
>
>
I've been fighting this error for a couple of years now and just when I think
I've got it understood and "Fixed", it bites me again.
Here's the error:
Exception ignored in:
Traceback (most recent call last):
File "X:\Python\python3.8\lib\tkinter\__init__.py", line 351, in __del__
i
