[issue12540] Restart Shell command leaves pythonw.exe processes running
Aneesh aneeshb...@gmail.com added the comment: I too retested this on a Windows 7 32 and 64 bit machines and is working fine when the provided PyShell.py is used. As Terry mentioned, IDLE seems be running better. The process in Task Manager disappears quickly after I close the IDLE. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12540 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12540] Restart Shell command leaves pythonw.exe processes running
Roundup Robot devn...@psf.upfronthosting.co.za added the comment: New changeset cc86f4ca5020 by Ned Deily in branch '3.2': Issue #12540: Prevent zombie IDLE processes on Windows due to changes http://hg.python.org/cpython/rev/cc86f4ca5020 New changeset c2fd1ce1c6d4 by Ned Deily in branch 'default': Issue #12540: Prevent zombie IDLE processes on Windows due to changes http://hg.python.org/cpython/rev/c2fd1ce1c6d4 -- nosy: +python-dev ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12540 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12540] Restart Shell command leaves pythonw.exe processes running
Ned Deily n...@acm.org added the comment: With Eli's concurrence, I have applied the updated patch to 3.2 (for 3.2.2) and to default (for 3.3). -- assignee: - ned.deily resolution: - fixed stage: commit review - committed/rejected status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12540 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12540] Restart Shell command leaves pythonw.exe processes running
Eli Bendersky eli...@gmail.com added the comment: On Fri, Aug 5, 2011 at 09:43, Ned Deily rep...@bugs.python.org wrote: Ned Deily n...@acm.org added the comment: With Eli's concurrence, I have applied the updated patch to 3.2 (for 3.2.2) and to default (for 3.3). -- Tested this on Windows XP with Python 3.2 installed into Program Files. Works fine (including shell restart). It would be great to get more people to test it though, especially people who ran into the problem originally - Peter? Terry? Anish? Qiang Sun? -- Added file: http://bugs.python.org/file22837/unnamed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12540 ___div dir=ltrdiv class=gmail_quoteOn Fri, Aug 5, 2011 at 09:43, Ned Deily span dir=ltrlt;a href=mailto:rep...@bugs.python.org;rep...@bugs.python.org/agt;/span wrote:brblockquote class=gmail_quote style=margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex; div class=imbr Ned Deily lt;a href=mailto:n...@acm.org;n...@acm.org/agt; added the comment:br br /divWith Eli#39;s concurrence, I have applied the updated patch to 3.2 (for 3.2.2) and to default (for 3.3).br br --br/blockquote/divbrTested this on Windows XP with Python 3.2 installed into quot;Program Filesquot;. Works fine (including shell restart).brbrIt would be great to get more people to test it though, especially people who ran into the problem originally - Peter? Terry? Anish? Qiang Sun?br brbrbr/div ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12540] Restart Shell command leaves pythonw.exe processes running
Terry J. Reedy tjre...@udel.edu added the comment: The replacement file, for anyone without a dev setup, is http://hg.python.org/cpython/file/cc86f4ca5020/Lib/idlelib/PyShell.py After renaming PyShell to PyShellBak and replacing with the above, IDLE seems to run better than ever. On my XP system, the several second delay for the old process dying is gone and I never see 3 pythonw processes, even temporarily, as before. I can no longer tell from TaskManager that one process has been killed and another started. Testing included running tk windows. Will test later on new Win7 system. Pending some unforeseen new problem, thank you Ned and Eli. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12540 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12540] Restart Shell command leaves pythonw.exe processes running
Peter Caven pca...@gmail.com added the comment: Terry, sorry about the delay in responding: I'm using 32bit Python. I haven't had a chance yet to try the 64 bit release. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12540 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12540] Restart Shell command leaves pythonw.exe processes running
Ned Deily n...@acm.org added the comment: I've added a couple of review comments to the one Peter already made in Rietveld. Here is an updated patch that addresses all of the comments. I've tested in briefly on Windows and on OS X and it seems to work OK. Eli, if you're OK with it, feel free to commit or I will do it. -- keywords: +3.2regression, patch -buildbot stage: needs patch - commit review versions: +Python 3.3 Added file: http://bugs.python.org/file22830/issue12540_rev2.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12540 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12540] Restart Shell command leaves pythonw.exe processes running
Eli Bendersky eli...@gmail.com added the comment: Terry, When I tried the same fix in idlelib/PyShell.py, adding 'import subprocess' and changing self.rpcpid = os.spawnv(os.P_NOWAIT, sys.executable, args) to self.rpcpid = subprocess.Popen(args).pid (args begins with sys.executable) IDLE failed to start. The only evidence that it had been invoked was a brief (1/4 second?) appearance of 1 pythonw process in task manager. On a subsequent tries, without touching the file, I do not see even that. Is there any obvious mistake in the above? No, when I do the same, things seem to go fine. No zombie is left running after IDLE is closed, and even Restart shell works without leaving a zombie. Maybe you had other modifications in your idlelib sources? Anyway, this wouldn't be a complete fix, because in: def unix_terminate(self): UNIX: make sure subprocess is terminated and collect status if hasattr(os, 'kill'): try: os.kill(self.rpcpid, SIGTERM) except OSError: # process already terminated: return else: try: os.waitpid(self.rpcpid, 0) except OSError: return os.waitpid on Windows also expects a process handle, not pid. I think the complete solution, in addition to replacing os.spawnv by subprocess.Popen, would be to use Popen.kill and then Popen.wait instead of os.kill and then os.wait in the code above. This would require keeping the Popen object somewhere in self. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12540 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12540] Restart Shell command leaves pythonw.exe processes running
Changes by STINNER Victor victor.stin...@haypocalc.com: -- nosy: -haypo ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12540 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12540] Restart Shell command leaves pythonw.exe processes running
Terry J. Reedy tjre...@udel.edu added the comment: I was working with the freshly reinstalled 3.2 which is not the same as a pristine 3.2 install because it still had the problem that 3.2.1 has and the 3.2.1 sys.version. 3.2.1 uninstall in not complete (a different issue). So I should reinstall 3.2.1 again and try again. I agree about fully switching t. subprocess. If self.rpcpid is not used anywhere other than unix_terminate (which I think should be renamed)), then self.subproc could replace self.rpcpid. -- keywords: +buildbot ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12540 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12540] Restart Shell command leaves pythonw.exe processes running
Eli Bendersky eli...@gmail.com added the comment: Attaching an initial patch for Lib/idlelib/PyShell.py It uses subprocess.Popen instead of spawnkill, in the way discussed in earlier messages. As far as I can tell, IDLE opens and restarts shells successfully, without leaving zombies behind. I only tested it on Windows, however, and due to the lack of unit tests for idlelib there wasn't much verification done. -- keywords: +patch Added file: http://bugs.python.org/file22799/issue12540.1.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12540 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12540] Restart Shell command leaves pythonw.exe processes running
Eli Bendersky eli...@gmail.com added the comment: I've now tested this on Ubuntu Linux as well. IDLE works, no zombies left behind. -- keywords: -patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12540 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12540] Restart Shell command leaves pythonw.exe processes running
Terry J. Reedy tjre...@udel.edu added the comment: I mentioned pipes because half of the subprocess chapter, it seems, talks about them. ASo I got the mis-impression that they are special for subprocess-started processes. But if the subprocess gets the args it needs to connect to a socket, it should not care how it is started. Anyway, some experiments: 3.1.3 and 3.1.4 freshly installed do not seem to have the zombie problem. This seems to rule out the possibility that the problem is due to recent patches from Microsoft. I redeleted 3.2 installation and re-installed 3.2. Sys.version still mistakingly say 3.2.1, July 10., so there is something different about the relationship between 3.2 and 3.2.1 and that between 3.1.3 and 3.1.4. And the 3.2 re-install has the zombie problem while I do not believe the fresh 3.2 install did. (And it does not on my other machine.) But I do not see how something stuck in the registry could affect process killing. In the notepad example, changing pid = os.spawnv(os.P_NOWAIT, 'C:/WINDOWS/notepad.exe', ['notepad.exe']) # (full path needed if not in /windows) to pid = subprocess.Popen(['C:/WINDOWS/notepad.exe']).pid changed the 'pid' from a constant (across multiple runs) to a variable (across multiple runs) and changed the result of the kill from a zombie and exception to proper termination. When I tried the same fix in idlelib/PyShell.py, adding 'import subprocess' and changing self.rpcpid = os.spawnv(os.P_NOWAIT, sys.executable, args) to self.rpcpid = subprocess.Popen(args).pid (args begins with sys.executable) IDLE failed to start. The only evidence that it had been invoked was a brief (1/4 second?) appearance of 1 pythonw process in task manager. On a subsequent tries, without touching the file, I do not see even that. Is there any obvious mistake in the above? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12540 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12540] Restart Shell command leaves pythonw.exe processes running
Eli Bendersky eli...@gmail.com added the comment: OK, I can reproduce the problem on a clean virtual machine running a pristine XP home SP2. No Python was previously installed. Steps to reproduce: 1. Install Python 3.2.1 MSI from http://www.python.org/download/releases/3.2.1/ 2. Run IDLE from start menu 3. Close IDLE 4. A pythonw.exe process stays running after IDLE has exited Running steps 2-3 N times leaves N pythonw.exe processes alive -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12540 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12540] Restart Shell command leaves pythonw.exe processes running
Eli Bendersky eli...@gmail.com added the comment: Am I missing something, or is there no explicit command to kill the subprocess on Windows in PyShell.py The kill_subprocess method (which does get invoked) of ModifiedInterpreter is: def kill_subprocess(self): try: self.rpcclt.close() except AttributeError: # no socket pass self.unix_terminate() self.tkconsole.executing = False self.rpcclt = None The subprocess is started with: self.rpcpid = os.spawnv(os.P_NOWAIT, sys.executable, args) Could it be that in earlier versions this ensured the subprocess exited with its parent, but this somehow got modified? Note that the same code existed in PyShell.py for ages, so it's unlikely that the culprit is there. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12540 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12540] Restart Shell command leaves pythonw.exe processes running
Ned Deily n...@acm.org added the comment: Doesn't unix_terminate() also get called on Windows? If so, what does os.kill() do on Windows? The docs for os.kill say New in version 3.2: Windows support. Perhaps this was being skipped before and now has some negative effect? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12540 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12540] Restart Shell command leaves pythonw.exe processes running
Eli Bendersky eli...@gmail.com added the comment: Indeed, unix_terminate is invoked on Windows, and since Windows now has os.kill it runs. However, it appears that the actual os.kill call throws OSError, saying: [Error 87] The parameter is incorrect -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12540 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12540] Restart Shell command leaves pythonw.exe processes running
Eli Bendersky eli...@gmail.com added the comment:
Here's a simple reproducer for the same problem, without the context of IDLE.
As far as I understand, what IDLE's spawn and then kill process are doing is:
import os
from signal import SIGTERM
pid = os.spawnv(os.P_NOWAIT, notepad.exe, ['notepad.exe'])
print('pid = %s, SIGTERM = %s' % (pid, SIGTERM))
os.kill(pid, SIGTERM)
Running this, the notepad.exe subprocess stays alive after the script exits,
and I get the error:
pid = 1868, SIGTERM = 15
Traceback (most recent call last):
File k.py, line 6, in module
os.kill(pid, SIGTERM)
WindowsError: [Error 87] The parameter is incorrect
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue12540
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12540] Restart Shell command leaves pythonw.exe processes running
Georg Brandl ge...@python.org added the comment: Hmm, the docs say Any other value for sig will cause the process to be unconditionally killed by the TerminateProcess API [...] What happens if you try to use other signals (like signal.SIGKILL) instead of SIGTERM? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12540 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12540] Restart Shell command leaves pythonw.exe processes running
Georg Brandl ge...@python.org added the comment: The other question is if it is an access control problem. win32_kill tries to open the process with PROCESS_ALL_ACCESS, while IMO PROCESS_TERMINATE would suffice. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12540 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12540] Restart Shell command leaves pythonw.exe processes running
Eli Bendersky eli...@gmail.com added the comment: Georg, I'm now debugging into win32_kill, and it's an error in OpenProcess, so this *could* be a security issue. The process is started with _spawnv, so maybe this causes problems opening it with OpenProcess later. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12540 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12540] Restart Shell command leaves pythonw.exe processes running
Eli Bendersky eli...@gmail.com added the comment: According to http://msdn.microsoft.com/en-us/library/7zt1y878%28v=vs.80%29.aspx, on Windows _spawnv in async mode (P_NOWAIT) returns the process _handle_, not the process ID. win32_kill uses OpenProcess, passing it pid to obtain the handle, but this pid is already the process handle. Removing the whole call to OpenProcess in win32_kill and passing pid (instead of handle) directly to TerminateProcess, solves the problem. So this appears to be a mismatch between os.spawnv and os.kill on windows. The fist returns the process handle, the second expects a process ID. Note that the documentation of os.spawnv mentions something about this: If mode is P_NOWAIT, this function returns the process id of the new process; [...] On Windows, the process id will actually be the process handle, so can be used with the waitpid() function. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12540 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12540] Restart Shell command leaves pythonw.exe processes running
Georg Brandl ge...@python.org added the comment: Hmm, on the other hand there may be valid use cases for using os.kill() with a PID. Argh. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12540 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12540] Restart Shell command leaves pythonw.exe processes running
Eli Bendersky eli...@gmail.com added the comment: I don't think there's a problem with os.spawnv and os.kill - they do what their docs describe. IMHO, the solution should be to change IDLE so that it uses subprocess.Popen for both starting and killing the child process. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12540 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12540] Restart Shell command leaves pythonw.exe processes running
Terry J. Reedy tjre...@udel.edu added the comment: Eli, nice detective work. What I understand is that there was a latent platform-dependent buglet that presumably got exposed by a recent change in process handling, as Ned suggested. idlelib/PyShell.py, class ModifiedInterpreter(InteractiveInterpreter) has def spawn_subprocess(self): if self.subprocess_arglist is None: self.subprocess_arglist = self.build_subprocess_arglist() args = self.subprocess_arglist self.rpcpid = os.spawnv(os.P_NOWAIT, sys.executable, args) so IDLE expects the return to always be a pid which it is not. Spawn_subprocess is called in both start_subprocess and restart_subprocess. Both now leave zombies on exit. I presume idlelib.run.main listens on the passed in port (in args) to make the connection. It appears to me that restart reuses the socket wrapped in self.rpcclt (rpc client). Using subprocess.Popen seems like an good idea. The subprocess module is explicitly intended to replace low-level, fragile, difficult to get right, usage of os.spawn* and similar. If it does not work for this problem, *it* should be fixed. On the other hand, IDLE uses sockets rather than pipes to communicate with subproccesses, perhaps because Windows pipes either are or were not as usable as unix pipes. Also, named or reusable pipes may not be usiversally available, so wrapping a pipe instead of a socket would, it seems to me, take more than simple replacement of spawnv by Popen. Kurt, what do you think about possible fixes to this bug (critical for using IDLE on Windows)? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12540 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12540] Restart Shell command leaves pythonw.exe processes running
Eli Bendersky eli...@gmail.com added the comment: Terry, What still bugs me is that it isn't clear what change from 3.2 to 3.2.1 caused this problem to manifest. Also, I'm not sure why you mention the sockets vs. pipes issue. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12540 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12540] Restart Shell command leaves pythonw.exe processes running
Eli Bendersky eli...@gmail.com added the comment: Is the problem happening only on 64-bit Windows, or 32-bit as well? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12540 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12540] Restart Shell command leaves pythonw.exe processes running
Qiang Sun sunqi...@gmail.com added the comment: I can reproduce this in 32-bit Windows XP Pro. SP3 -- nosy: +sunqiang ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12540 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12540] Restart Shell command leaves pythonw.exe processes running
Terry J. Reedy tjre...@udel.edu added the comment: Good question. Peter, you said Vista x64. Are you running 32 or 64 bit Python? My system with the apparently irreversible problem is 32 bit xp home. I am reluctant to test on my daughter's 64 bit laptop as I do not know that I would be able to revert successfully and I want her to be able to write small programs for schoolwork without extra hassle. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12540 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12540] Restart Shell command leaves pythonw.exe processes running
Terry J. Reedy tjre...@udel.edu added the comment: This nasty bug really can cause severe problems. If a zombie process ran a tkinter (tk) window, then attempting to logout/restart/shutdown eventually brings up a window I have never seen before: End Process -- EmbeddedMenuWindow. The message window shows a countdown timer that implies that it will shutdown the process automatically when the timer reaches 0. But it does not because the process does not respond. It will sit there indefinitely. One has to click a shutdown button to get rid of it. Then a few seconds later, another window for the next zombie appears. And so on. It there are 50 zombies, then one would have to repeat 50 times. Not acceptible to me. Since IDLE is my Python workspace and since I plan to soon start running lots of tkinter tests and experiments soon, I am reverting to 3.2.0 until there is a fixed Windows binary. Adding the two listed Windows experts. -- nosy: +brian.curtin, tim.golden ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12540 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12540] Restart Shell command leaves pythonw.exe processes running
Terry J. Reedy tjre...@udel.edu added the comment: Restart is not required to create a zombie. Just start IDLE and quit, and the second, user process does not disappear. Reverting completely does not seem possible. I first just ran the 3.2 installer and it did not complain, that I noticed, about replacing a newer version, but apparently only replaced .exe and .dll and a few other files but not Lib/*.py. Idle or command prompt window said it was still 3.2.1 and the bug remained. So I uninstalled, deleted everything left except my .py files in site-packages and another subdirectory, and reinstalled 3.2. Now everything seems to predate 2/22/2011. BUT IDLE and command prompt window *still* report Python 3.2.1 (default, Jul 10 2011, 21:51:15) [MSC v.1500 32 bit (Intel)] on win32. This is sys.version. Something somewhere (registry?) seems to not be deleted by uninstall. And the bug remains. Could a registry entry possibly affect this? My system is 7 years old with updated win xp 32 bit. I then checked the never updated 64 bit Py 3.2 on an 18 month old 64 bit Win 7 laptop and detached user processes *do* disappear as I remember on this machine. It did, however, take 8 sec over restart and 12 after closing, which is longer than I remember for my older and definitely slower machine. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12540 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12540] Restart Shell command leaves pythonw.exe processes running
Changes by Eli Bendersky eli...@gmail.com: -- nosy: +eli.bendersky ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12540 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12540] Restart Shell command leaves pythonw.exe processes running
Aneesh aneeshb...@gmail.com added the comment: We are also noticed same issue and reverted to Python 3.1. Whenever we run a script, two new pythonw.exe process is started and it is really irritating to see all in Windows Task Manager. Last day I killed around 14 Pythonw.exe to clean up everything. -- nosy: +Aneesh ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12540 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12540] Restart Shell command leaves pythonw.exe processes running
Ned Deily n...@acm.org added the comment: This appears to be a Windows-only issue; I'm not able to readily reproduce it on either Linux or OS X. Taking a quick look at diffs between 3.2 and 3.2.1, there aren't a lot of changes in IDLE (Lib/idlelib) and nothing obviously related. There are a number of changes elsewhere in signal handling and process handling, though. The restart_subprocess code is in Lib/idlelib/PyShell.py. If there isn't anything obvious elsewhere, perhaps someone can try to hg bisect it on Windows. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12540 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12540] Restart Shell command leaves pythonw.exe processes running
Martin v. Löwis mar...@v.loewis.de added the comment: FWIW, it only happens with IDLE; python.exe seems to terminate fine when done. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12540 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12540] Restart Shell command leaves pythonw.exe processes running
Martin v. Löwis mar...@v.loewis.de added the comment: Terry, please don't overreact. Nobody has noticed it during the *long* rc period of 3.2.1, so it can't be that bad. Actually, I *did* notice, but didn't have the time to submit a bug report. -- priority: critical - high ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12540 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12540] Restart Shell command leaves pythonw.exe processes running
Terry J. Reedy tjre...@udel.edu added the comment: I just 'upgraded' to 3.2.1 on my XP machine and I see the same with F5-run, which restarts before running the saved file. This appears to be a nasty regression from 3.2.0 that should have been a release blocker if caught earlier. I believe it merits a quick re-release, once fixed, of either the Windows binary or Python itself depending on whether this is windows specific or not. The normal behavior when starting IDLE is 2 pythonw.exe processes -- one to run IDLE itself and the other for the attached process that runs user code. Restart/Run starts a third process with a fresh interpreter for user code and the old, orphaned user process should and usually does disappear in 2-3 seconds (on my old, slow machine). (There are tracker issues about this not always happening when a runaway process is stopped with ^C, but is has always worked otherwise.) Each process appears to take about 10+Mb, so anyone doing rapid code/test iterations, as I sometimes do, could easily overfill physical memory. Closing the IDLE windows does not stop the detached processes, so they have to be killed 1 at a time with 3 clicks each or by rebooting. Neither is pleasant. Although I should have 3.2.1 loaded at least for reviewing issues, I plan to revert to 3.2.0. Victor: do you know of any way to test for process extinction on Windows? -- nosy: +georg.brandl, haypo, kbk, loewis, terry.reedy priority: normal - critical stage: - needs patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12540 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12540] Restart Shell command leaves pythonw.exe processes running
Changes by Georg Brandl ge...@python.org: -- nosy: +ned.deily ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12540 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12540] Restart Shell command leaves pythonw.exe processes running
New submission from Peter Caven pca...@gmail.com: On Windows Vista (x64) the IDLE Restart Shell command leaves a pythonw.exe process running each time that the command is used. Observed in Python 3.2.1 release and RC2. -- components: IDLE messages: 140179 nosy: Peter.Caven priority: normal severity: normal status: open title: Restart Shell command leaves pythonw.exe processes running type: resource usage versions: Python 3.2 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12540 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
