[Python-bugs-list] [ python-Bugs-216289 ] Programs using Tkinter sometimes can't shut down (Windows)
noreply@sourceforge.net
noreply@sourceforge.net
Tue, 02 Jul 2002 12:39:45 -0700
Bugs item #216289, was opened at 2000-10-06 22:25
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=216289&group_id=5470
Category: Windows
Group: Python 2.3
Status: Open
Resolution: Later
Priority: 3
Submitted By: Tim Peters (tim_one)
>Assigned to: Fredrik Lundh (effbot)
Summary: Programs using Tkinter sometimes can't shut down (Windows)
Initial Comment:
The following msg from the Tutor list is about 1.6, but I noticed the same thing several times today using 2.0b2+CVS. In my case, I was running IDLE via
python ../tool/idle/idle.pyw
from a DOS box in my PCbuild directory. Win98SE. *Most* of the time, shutting down IDLE via Ctrl+Q left the DOS box hanging. As with the poster, the only way to regain control was to use the Task Manager to kill off Winoldap.
-----Original Message-----
From: Joseph Stubenrauch <nothingisgoingtochangemyworld@yahoo.com>
Sent: Friday, October 06, 2000 9:23 PM
To: tutor@python.org
Subject: Re: [Tutor] Python 1.6 BUG
Strange, I have been experiencing the same bug myself.
Here's the low down for me:
Python 1.6 with win95
I am running a little Tkinter program
The command line I use is simply: "python foo.py"
About 25-35% of the time, when I close the Tkinter
window, DOS seems to "freeze" and never returns to the
c:\ command prompt. I have to ctrl-alt-delete
repeatedly and shut down "winoldapp" to get rid of the
window and then shell back into DOS and keep working.
It's a bit of a pain, since I have the habit of
testing EVERYTHING in tiny little stages, so I change
one little thing, test it ... freeze ... ARGH! Change
one more tiny thing, test it ... freeze ... ARGH!
However, sometimes it seems to behave and doesn't
bother me for an entire several hour session of python
work.
That's my report on the problem.
Cheers,
Joe
----------------------------------------------------------------------
>Comment By: Tim Peters (tim_one)
Date: 2002-07-02 15:39
Message:
Logged In: YES
user_id=31435
Jeff, a long time ago Fredrik Lundh said he was able to
reproduce this with a short wish script (no Python, no Tkinter,
just Tcl/Tk + wish). I'm reassigning this to /F in the hopes
he'll remember how.
----------------------------------------------------------------------
Comment By: Jeffrey Hobbs (hobbs)
Date: 2002-07-02 14:55
Message:
Logged In: YES
user_id=72656
I appreciate that many others see this is a problem in
embedding Tcl, but without any clear way to reproduce this in
Tcl/Tk itself, it's very hard for me to fix it. I don't think that
there is anything done in 8.4 to fix this that I recall, but if
someone finds that the problem "goes away" with 8.4, please
report that.
For those of course that experience this with python, the
simple and "correct" work-around is to launch with
pythonw.exe instead of python.exe.
----------------------------------------------------------------------
Comment By: Nobody/Anonymous (nobody)
Date: 2002-06-26 13:40
Message:
Logged In: NO
According to http://tcl.activestate.com ActiveTcl 8.4.0 is now
available for download. It is new as of June 24. I don't know
whether this will solve our problems or not, but it's worth
looking into.
----------------------------------------------------------------------
Comment By: Nobody/Anonymous (nobody)
Date: 2002-06-19 09:36
Message:
Logged In: NO
I just downloaded Ruby 1.6.6 for Windows, which also uses
Tcl/Tk 8.3 and I experience exactly the same problem there.
So this is definitely a Tcl problem (but we know that already).
----------------------------------------------------------------------
Comment By: John Popplewell (johnnypops)
Date: 2002-06-07 15:01
Message:
Logged In: YES
user_id=143340
Hmmm.
I run a Python Tcl/Tk application several times every day -
the very application that prompted my bug-hunt.
I do use "pythonw.exe" to launch it, but it used to hang
almost as badly as "python.exe".
Whilst developing this app I used "python.exe" and
experienced no hang-ups.
The Tcl guys point out that this bug is only one of several
possible causes of the hang-up, maybe you are just out of
luck.
The patch has fixed the problem on three Win98 machines,
all of which exhibited the problem before updating the DLLs.
One thought - are you sure there weren't multiple copies of
the tcl83.dll and tk83.dll files? My (only) copies were
in "D:\python20\DLLs"
good luck,
John.
----------------------------------------------------------------------
Comment By: Jeffrey Hobbs (hobbs)
Date: 2002-06-03 14:55
Message:
Logged In: YES
user_id=72656
providing Tim with a fixed DLL exactly according to John
Popplewell's patch did not fix the problem for him. That
makes it seem fishy that John really didn't see the problem
any more.
----------------------------------------------------------------------
Comment By: Tim Peters (tim_one)
Date: 2002-06-03 12:59
Message:
Logged In: YES
user_id=31435
I tried replacing Python 2.2.1's tk83.dll and tcl83.dll (from
Tcl/Tk 8.3.2) with newer matched sets from
A) PythonWare's py21 distribution (Tcl/Tk 8.3.3).
and again from
B) ActiveState's Tcl/Tk 8.3.4.
All the symptoms originally reported here persisted on
Win98SE despite that.
----------------------------------------------------------------------
Comment By: Nobody/Anonymous (nobody)
Date: 2002-05-22 09:57
Message:
Logged In: NO
I am new to Python and encountered this bug on my very first
Tkinter application. It persists in Python 2.2.1 under
Windows Me. Needless to say, it makes a bad first
impression. Basically, this thread says that Tkinter has been
broken for a year and a half on a popular platform at a time
when Python is trying to expand its user base. Hopefully, this
bug will be corrected soon.
If Tcl/Tk 8.4 is not released shortly you might try repackaging
Tkinter for Win32 with an earlier version of Tcl/Tk, such as
8.0, that doesn't encounter this problem.
----------------------------------------------------------------------
Comment By: Guido van Rossum (gvanrossum)
Date: 2002-03-22 22:36
Message:
Logged In: YES
user_id=6380
The proper action is to wait until Tcl 8.3.5 is released,
and then shaming someone else in providing you with a set of
Windowsbinaries for Tcl. You may also ask Hobbs if there's a
Windows project file to build Tcl/Tk for Windows.
----------------------------------------------------------------------
Comment By: Jeffrey Hobbs (hobbs)
Date: 2002-03-11 21:31
Message:
Logged In: YES
user_id=72656
I did end up back-porting this to the 8.3.4+ Tcl CVS on
2002-02-25, which means it will be in an eventual 8.3.5.
It is already in the release 8.4 alpha series.
----------------------------------------------------------------------
Comment By: Tim Peters (tim_one)
Date: 2002-03-09 20:50
Message:
Logged In: YES
user_id=31435
Back to Guido: Do you think you know what the proper
action is? (You said that's why you reopened it, and
there's been no new info here since then.)
----------------------------------------------------------------------
Comment By: John Popplewell (johnnypops)
Date: 2002-02-25 19:55
Message:
Logged In: YES
user_id=143340
I knew I wasn't getting to the heart of it ....
Almost a one-liner!
It has been seriously spoiling my (otherwise crash free)
Python experience on Win9x - hope it gets fixed soon.
cheers,
John.
----------------------------------------------------------------------
Comment By: Guido van Rossum (gvanrossum)
Date: 2002-02-25 18:39
Message:
Logged In: YES
user_id=6380
Reopened until we know what the proper action is.
----------------------------------------------------------------------
Comment By: Jeffrey Hobbs (hobbs)
Date: 2002-02-25 18:32
Message:
Logged In: YES
user_id=72656
This is mostly correct, and is fixed in the 8.4 Tcl sources
already (I guess we can backport this). This was mentioned
in SF Tcl bug (account for chopped URL):
https://sourceforge.net/tracker/?
func=detail&aid=217982&group_id=10894&atid=110894
and the code comment is:
/*
* Only finalize the notifier if a notifier was
installed in the
* current thread; there is a route in which this is not
* guaranteed to be true (when tclWin32Dll.c:DllMain()
is called
* with the flag DLL_PROCESS_DETACH by the OS, which
could be
* doing so from a thread that's never previously been
involved
* with Tcl, e.g. the task manager) so this check is
important.
*
* Fixes Bug #217982 reported by Hugh Vu and Gene
Leache.
*/
if (tsdPtr == NULL) {
return;
}
----------------------------------------------------------------------
Comment By: John Popplewell (johnnypops)
Date: 2002-02-25 17:41
Message:
Logged In: YES
user_id=143340
This one has been torturing me for a while.
Managed to track it down to a problem inside Tcl.
For the Tcl8.3.4 source distribution the problem is in
the file win/tclWinNotify.c
void Tcl_FinalizeNotifier(ClientData clientData)
{
ThreadSpecificData *tsdPtr =
(ThreadSpecificData *) clientData;
/* sometimes called with tsdPtr == NULL */
if ( tsdPtr != NULL )
{
DeleteCriticalSection(&tsdPtr->crit);
CloseHandle(tsdPtr->event);
/*
* Clean up the timer and messaging
* window for this thread.
*/
if (tsdPtr->hwnd) {
KillTimer(tsdPtr->hwnd, INTERVAL_TIMER);
DestroyWindow(tsdPtr->hwnd);
}
}
/*
* If this is the last thread to use the notifier,
* unregister the notifier window class.
*/
Tcl_MutexLock(¬ifierMutex);
if ( notifierCount && !--notifierCount ) {
UnregisterClassA( "TclNotifier",
TclWinGetTclInstance());
}
Tcl_MutexUnlock(¬ifierMutex);
}
This bodge doesn't address the underlying problem but has
stopped me from tearing all my hair out,
cheers,
John Popplewell.
----------------------------------------------------------------------
Comment By: Tim Peters (tim_one)
Date: 2001-10-24 18:27
Message:
Logged In: YES
user_id=31435
FYI, you don't need an IDE to do this -- in Win9x, hit
Ctrl+Alt+Del and kill the process directly.
A saner <wink> solution is to develop under Win2K, which
doesn't appear to suffer this problem (the only reports
I've seen, and experienced myself, came from Win9x boxes).
----------------------------------------------------------------------
Comment By: Nobody/Anonymous (nobody)
Date: 2001-10-24 04:52
Message:
Logged In: NO
For those who are still trapped in this bug's hell, I will
gladly share the one thing that saved my sanity:
WingIDE's 'Kill' command will shut down the program with
apparent 100% certainty and no fear of lockups. WingIDE
has its own issues, so its not a perfect solution, but if
you are like me and Joe (above) who test in small
iterations, then using 'Kill' to quit out of your app while
testing is a workaround that may preserve your sanity.
Perhaps the python gods and the Wing guys can get together
and tell us how to replicate 'kill' into our code. For
now, I'll use WingIDE to edit, and pythonw.exe for my final
client's delivery.
----------------------------------------------------------------------
Comment By: Howard Lightstone (hlightstone)
Date: 2001-09-05 13:43
Message:
Logged In: YES
user_id=66570
I sometimes get bunches of these....
A tool I use (Taskinfo2000) reports that (after killing
winoldap):
python.exe is blocked on a mutex named OLESCELOCKMUTEX.
The reported state is "Console Terminating". There appears
to be only one (os) thread running.
----------------------------------------------------------------------
Comment By: Tim Peters (tim_one)
Date: 2001-04-02 16:06
Message:
Logged In: YES
user_id=31435
No sign of progress on this presumed Tk/Tcl Windows bug in
over 3 months, so closing it for lack of hope.
----------------------------------------------------------------------
Comment By: Doug Henderson (djhender)
Date: 2001-02-06 00:13
Message:
This was a symptom I saw while tracking down the essence of the problem reported in #131207. Using Win98SE, I would get an error dialog (GPF?) in the Kernel, and sometimes the dos prompt would not come back.
----------------------------------------------------------------------
Comment By: Tim Peters (tim_one)
Date: 2000-12-12 21:00
Message:
Just reproduced w/ current CVS, but didn't hang until the 8th try.
http://dev.scriptics.com/software/tcltk/ says 8.3 is still the latest released version; don't know whether that URL still makes sense, though.
----------------------------------------------------------------------
Comment By: Guido van Rossum (gvanrossum)
Date: 2000-12-12 15:58
Message:
Tim, can you still reproduce this with the current CVS version?
There's been one critical patch to _tkinter since the 2.0 release.
An alternative would be to try with a newer version of Tcl (isn't 8.4 out already?).
----------------------------------------------------------------------
Comment By: Nobody/Anonymous (nobody)
Date: 2000-10-15 12:47
Message:
Same as I've reported earlier; it hangs in the call to
Tcl_Finalize (which is called by the DLL finalization
code). It's less likely to hang if I call Tcl_Finalize
from the _tkinter DLL (from user code).
Note that the problem isn't really Python-related -- I
have stand-alone samples (based on wish) that hangs in
the same way.
More later.
</F>
----------------------------------------------------------------------
Comment By: Guido van Rossum (gvanrossum)
Date: 2000-10-13 10:40
Message:
Back to Tim since I have no clue what to do here.
----------------------------------------------------------------------
Comment By: Guido van Rossum (gvanrossum)
Date: 2000-10-12 13:25
Message:
The recent fix to _tkinter (Tcl_GetStringResult(interp) instead of interp->result) didn't fix this either.
As Tim has remarked in private but not yet recorded here, a workaround is to use pythonw instead of python, so I'm lowering thepriority again.
Also note that the hanging process that Tim writes about apparently prevents Win98 from shutting down properly.
----------------------------------------------------------------------
Comment By: Tim Peters (tim_one)
Date: 2000-10-07 03:37
Message:
More info (none good, but some worse so boosted priority):
+ Happens under release and debug builds.
+ Have not been able to provoke when starting in the debugger.
+ Ctrl+Alt+Del and killing Winoldap is not enough to clean everything up. There's still a Python (or Python_d) process hanging around that Ctrl+Alt+Del doesn't show.
+ This process makes it impossible to delete the associated Python .dll, and in particular makes it impossible to rebuild Python successfully without a reboot.
+ These processes cannot be killed! Wintop and Process Viewer both fail to get the job done. PrcView (a freeware process viewer) itself locks up if I try to kill them using it. Process Viewer freezes for several seconds before giving up.
+ Attempting to attach to the process with the MSVC debugger (in order to find out what the heck it's doing) finds the process OK, but then yields the cryptic and undocumented error msg "Cannot execute program".
+ The processes are not accumulating cycles.
+ Smells like deadlock.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=216289&group_id=5470