Joe Gaspard added the comment:
Thanks Terry. As best I can recall was trying to save a ".py" while
IDLE and the "'.py" file were both open, but definitely not a
'Library' file. I did try to save the IDLE window display once, and
it may have been this time. My programs have been much smaller than
400000 lines (53 KB max), but I have saved a 500 billion byte file on
the same 2TB hard drive without a problem.
Attached is a WordPad doc describing two additional problems that
happened a little while ago. Python is new to me. Would I have
fewer problems if I used an earlier version? Thanks again for the
help .... Joe Gaspard
At 03:57 PM 8/1/2014, you wrote:
>Terry J. Reedy added the comment:
>
>What file were you trying to save to? Be very exact. Reading/Saving
>to 'Library' files is known to have problems and there is another
>issue for this.
>
>Were you trying to save the Shell window, displaying output from
>your program.
>
>What is the minimum # of lines required to have a problem. 400000
>lines is probably "won't fix" because the problem is likely with tk
>and Windows, not Idle. Your program should print directly to a file.
>
>----------
>nosy: +terry.reedy
>title: Hang during File "Save As" -> Idle: Hang during File "Save As"
>
>_______________________________________
>Python tracker <rep...@bugs.python.org>
><http://bugs.python.org/issue22105>
>_______________________________________
----------
Added file: http://bugs.python.org/file36242/PythonHang201408011146.txt
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue22105>
_______________________________________
APP HANG 8/1/2014 11:46-47 AM
WHILE IN IDLE: Selected Edit>Find> x. Program did not respond.
Program was manually interrupted by "CTRL.C" (while in Python
3.4.1 shell) prior to attempting a search for a variable
"x", probably (but not exactly) similar to pervious "Hang" problem submitted
to Python. Moving the cursor to the ">>>_" position on the display relieved the
Problem. Fortunately the operating program was saved before the problem
occurred. The operating program was lost last time this
happened. "I am not going to do that anymore." Hope this info helps. ... Joe
Gaspard
See Microsoft report below for more details.
Description:
A problem caused this program to stop interacting with Windows.
Problem signature:
Problem Event Name: AppHangB1
Application Name: pythonw.exe
Application Version: 0.0.0.0
Application Timestamp: 5378731e
Hang Signature: 1910
Hang Type: 0
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033
Additional Hang Signature 1: 191017f5c54030d20a7f882b139dfba9
Additional Hang Signature 2: 184f
Additional Hang Signature 3: 184f1a21fed89659658cbe7167f7508c
Additional Hang Signature 4: 1910
Additional Hang Signature 5: 191017f5c54030d20a7f882b139dfba9
Additional Hang Signature 6: 184f
Additional Hang Signature 7: 184f1a21fed89659658cbe7167f7508c
Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409
If the online privacy statement is not available, please read our privacy
statement offline:
C:\Windows\system32\en-US\erofflps.txt
8/3/2014 7:30 PM - Uninitiated program stop:
"Your computer is low on memory"
"The ecception breakpoint has been reached"
(0X80000003 occured in the application at
location 0x74c54164)
Click OK to terminate the program
I first cleared the (!) Low Memory pop-up, then the (X)Exception breakpoint
pop-up. Normal activity Ok afterwards.
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
