[issue2584] numeric overflow in IDLE
Tim Wilcoxson <[EMAIL PROTECTED]> added the comment: I guess my only reply isfair enough. heh. On Thu, May 22, 2008 at 1:07 PM, Kurt B. Kaiser <[EMAIL PROTECTED]> wrote: > > Kurt B. Kaiser <[EMAIL PROTECTED]> added the comment: > > When this is running, what happens if you hit Control-c a few times, > especially in the first few seconds? Does it abort with a > KeyboardInterrupt? Does it stop responding to Control-c after the window > fills up? > > Note that IDLE slows down when very large quantities of text are printed > to the shell window. This is an issue with the Tk library. > > The subprocess is supposed to exit when it notices that the socket has > closed. This doesn't work well on Windows, unfortunately. We are > thinking about it ;-) > > It doesn't seem that what you are attempting to fix has any realistic > application. > > I don't run Vista. Check your resources right after you start your > code. Is your system unresponsive because you are running out of memory > or because you are using CPU 100%? > > > Patient: My head hurts when I bang it against a wall. > Doctor: So, don't do that! > > __ > Tracker <[EMAIL PROTECTED]> > <http://bugs.python.org/issue2584> > __ > Added file: http://bugs.python.org/file10409/unnamed __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue2584> __I guess my only reply isfair enough. heh.On Thu, May 22, 2008 at 1:07 PM, Kurt B. Kaiser <mailto:[EMAIL PROTECTED]">[EMAIL PROTECTED]> wrote: Kurt B. Kaiser <mailto:[EMAIL PROTECTED]">[EMAIL PROTECTED]> added the comment: When this is running, what happens if you hit Control-c a few times, especially in the first few seconds? Does it abort with a KeyboardInterrupt? Does it stop responding to Control-c after the window fills up? Note that IDLE slows down when very large quantities of text are printed to the shell window. This is an issue with the Tk library. The subprocess is supposed to exit when it notices that the socket has closed. This doesn't work well on Windows, unfortunately. We are thinking about it ;-) It doesn't seem that what you are attempting to fix has any realistic application. I don't run Vista. Check your resources right after you start your code. Is your system unresponsive because you are running out of memory or because you are using CPU 100%? Patient: My head hurts when I bang it against a wall. Doctor: So, don't do that! __ Tracker <mailto:[EMAIL PROTECTED]">[EMAIL PROTECTED]> <http://bugs.python.org/issue2584"; target="_blank">http://bugs.python.org/issue2584> __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2584] numeric overflow in IDLE
New submission from Tim Wilcoxson <[EMAIL PROTECTED]>: According to the documentation there is not suppose to be numeric overflow in python 2.5. However If you run a for loop with the range(1, 3)a couple of times (for me 2 or 3 times worked) in the IDLE (1.2.2)GUI . It will cause what appears to be a memory leak, at least under vista home edition. Haven't tested out other platforms yet. Vista's logon process will fail to start security dialog as well if you try to ctrl-alt-del. Which effectively cripples the system. I haven't tested to see if the condition will get better over long period of time. I've waited a max of 10 minutes for the system to respond. I tested running the script multiple times under cmd in windows, and it spits out a memory error after a minute of not responding and then the cmd prompts will close and the system will begin responding. So it appears to be isolated to IDLE. -- components: IDLE files: for_loop.py messages: 65167 nosy: Qodosh severity: normal status: open title: numeric overflow in IDLE type: crash versions: Python 2.5 Added file: http://bugs.python.org/file9982/for_loop.py __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue2584> __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2584] numeric overflow in IDLE
Tim Wilcoxson <[EMAIL PROTECTED]> added the comment: msg65177, i did try to close cmd. thats why it closed. i wasnt clear enough. my apologies. it merely lags in command line in gives a memory error. in IDLE, it wont respond, and it gives a logon process erorr in windows if you try to view the security dialog. Let's just say this. i got dressed, walked out my apartment several flights of strairs, went across a large parking lot, grabbed a bag, came back, got comfortable, looked at my computer, and it was still completely unresponsive. I did this several times, same problem. __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue2584> __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2584] numeric overflow in IDLE
Tim Wilcoxson <[EMAIL PROTECTED]> added the comment: not a nick aye? lol. I am new cant you tell. And when i ran the script nothing could be closed. And, yes, I realize it could be a memory exhaustion issue with windows. windows is notorious for crappy resource handling. However, my concern came when I actually got an error and a clean exit with cmd prompt but not with the GUI. explorer.exe didn't crash. And I've had memory exhaustion under windows before, and it still allowed me enough memory to (albeit slowly) ctrl-alt-del. However the login process wouldnt even function. I did try xrange, it hung as the other. __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue2584> __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
