After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 106460 - Terminal hangs with repeated "Error reading from child: Bad address"
Terminal hangs with repeated "Error reading from child: Bad address"
Status: RESOLVED DUPLICATE of bug 108660
Product: vte
Classification: Core
Component: general
unspecified
Other Linux
: High major
: ---
Assigned To: VTE Maintainers
Nalin Dahyabhai
Depends on:
Blocks:
 
 
Reported: 2003-02-18 22:10 UTC by Olav Vitters
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.1/2.2


Description Olav Vitters 2003-02-18 22:10:37 UTC 
On heavy screenoutput, vte 0.10.20 hangs. When this happens the following
error message is repeatedly (100+ times/sec) written to ~/.xsession-errors:
** (gnome-terminal:2019): WARNING **: Error reading from child: Bad address.

The problem seems to be gone after manually compiling vte 0.10.19.

To reproduce:
1. Start mc (Midnight Commander)
(usually hangs up when starting mc)

Another way to reproduce:
1. Make a new gnome-terminal profile which starts /usr/bin/mutt -y (Mutt)
2. Start a new gnome-terminal window with that profile
3. Create 3 additional tabs (with the same profile)
4. For each tab, select a mailbox
   This causes Mutt to print out how many mails it has read (lots of screen
output)

And another:
1. less /usr/share/dict/word
2. Scroll up and down

When a gnome-terminal/vte tab hangs, writes the error and uses 100% CPU.
After closing the hanging tab with Control-Shift-W, the CPU usage drops
back to normal levels and the error isn't written anymore.

Note: when a tab hangs, the other tabs usually aren't affected.
Comment 1 Olav Vitters 2003-02-18 22:39:42 UTC 
> When a gnome-terminal/vte tab hangs, writes the error and uses 100% CPU.

When a gnome-terminal/vte tab hangs, it writes the error to
~/.xsession-errors and uses 100% CPU.
Comment 2 toshok 2003-03-20 03:38:30 UTC 
108660 contains a patch that should fix this problem.
Comment 3 Olav Vitters 2003-03-21 05:20:13 UTC 
Compiled vte 0.10.26 with and without the patch from bug 108660.

Patch fixed it.

Duping to bug with patch

*** This bug has been marked as a duplicate of 108660 ***