[Python-bugs-list] [ python-Bugs-216289 ] Programs using Tkinter sometimes can't shut down (Windows) (original) (raw)

noreply@sourceforge.net noreply@sourceforge.net
Wed, 24 Oct 2001 15:27:42 -0700

Bugs item #216289, was opened at 2000-10-06 19:25 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=105470&aid=216289&group_id=5470

Category: Windows Group: 3rd Party Status: Closed Resolution: Wont Fix Priority: 3 Submitted By: Tim Peters (tim_one) Assigned to: Tim Peters (tim_one) 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 (timone) Date: 2001-10-24 15: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 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 01: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 10: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 13: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-05 21: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 18: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 12: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 09: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.

Comment By: Guido van Rossum (gvanrossum) Date: 2000-10-13 07:40

Message: Back to Tim since I have no clue what to do here.

Comment By: Guido van Rossum (gvanrossum) Date: 2000-10-12 10: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 00:37

Message: More info (none good, but some worse so boosted priority):

You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=105470&aid=216289&group_id=5470