[ python-Bugs-1092225 ] IDLE hangs due to subprocess

SourceForge.net noreply at sourceforge.net
Tue Dec 28 16:31:53 CET 2004


Bugs item #1092225, was opened at 2004-12-28 16:31
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1092225&group_id=5470

Category: IDLE
Group: Python 2.3
Status: Open
Resolution: None
Priority: 5
Submitted By: ZACK (kitanek)
Assigned to: Nobody/Anonymous (nobody)
Summary: IDLE hangs due to subprocess

Initial Comment:
IDLE GUI hangs after some time when launched in the
default mode (i.e. with the subprocess).
I have noticed that the subprocess generates fast
continuous stream of system calls even if the GUI is
not used and not visible (moved to another desktop).
Example output from strace (strace -f idle):

...
[pid  5359] <... select resumed> )      = 0 (Timeout)
[pid  5359] futex(0x81fb798, FUTEX_WAKE, 1) = 0
[pid  5359] futex(0x81fb798, FUTEX_WAKE, 1) = 0
[pid  5359] futex(0x81fb798, FUTEX_WAKE, 1) = 0
[pid  5359] select(4, [3], [], [], {0, 50000}
<unfinished ...>
[pid  5355] <... futex resumed> )       = -1 ETIMEDOUT
(Connection timed out)
[pid  5355] write(7, "\0", 1 <unfinished ...>
[pid  5356] <... select resumed> )      = 1 (in [6])
[pid  5355] <... write resumed> )       = 1
[pid  5356] futex(0x81c7250, FUTEX_WAIT, 2, NULL
<unfinished ...>
[pid  5355] futex(0x81c7250, FUTEX_WAKE, 1 <unfinished ...>
[pid  5356] <... futex resumed> )       = -1 EAGAIN
(Resource temporarily unavailable)
[pid  5355] <... futex resumed> )       = 0
[pid  5356] futex(0x81c7250, FUTEX_WAKE, 1 <unfinished ...>
[pid  5355] gettimeofday( <unfinished ...>
[pid  5356] <... futex resumed> )       = 0
[pid  5355] <... gettimeofday resumed> {1104246902,
467914}, {4294967236, 0}) = 0
[pid  5356] read(6,  <unfinished ...>
[pid  5355] gettimeofday( <unfinished ...>
[pid  5356] <... read resumed> "\0", 1) = 1
[pid  5355] <... gettimeofday resumed> {1104246902,
468040}, {4294967236, 0}) = 0
[pid  5356] select(7, [6], [], [], NULL <unfinished ...>
[pid  5355] select(6, [5], [], [], {0, 50000}
<unfinished ...>
[pid  5357] <... select resumed> )      = 0 (Timeout)
[pid  5357] futex(0x81fb798, FUTEX_WAKE, 1) = 0
[pid  5357] futex(0x81fb798, FUTEX_WAKE, 1) = 0
[pid  5357] select(0, NULL, NULL, NULL, {0, 50000}
<unfinished ...>
[pid  5359] <... select resumed> )      = 0 (Timeout)
[pid  5359] futex(0x81fb798, FUTEX_WAKE, 1) = 0
[pid  5359] futex(0x81fb798, FUTEX_WAKE, 1) = 0
[pid  5359] futex(0x81fb798, FUTEX_WAKE, 1) = 0
...

If IDLE is launched without the subprocess (idle -n)
than it seems to run just fine without the syscall storm:

futex(0x83d1fa0, FUTEX_WAIT, 200, NULL



----------------------------------------------------------------------

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


More information about the Python-bugs-list mailing list