Bug 79723 - gnome-terminal consumes all memory
Summary: gnome-terminal consumes all memory
Keywords:
Status: CLOSED DUPLICATE of bug 76219
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: Xft
Version: 8.0
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Owen Taylor
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-12-16 06:38 UTC by John Newbigin
Modified: 2008-05-01 15:38 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2006-02-21 18:50:21 UTC
Embargoed:


Attachments (Terms of Use)

Description John Newbigin 2002-12-16 06:38:37 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20021003

Description of problem:
quite frequently, gnome-terminal starts consuming memory, causing the machine to
start grinding the swap and running like a dog.  If you can manage to switch
back to the console and run top, gnome-terminal is using over 600M of ram.  Some
time later, gnome terminal dies, along with any children.

Version-Release number of selected component (if applicable):


How reproducible:
Sometimes

Steps to Reproduce:
1.run gnome-terminal
2.wait
    

Actual Results:  gnome-terminal dies.  I don't know if it dies it's self or
something (the kernel) kills it.

Expected Results:  gnome-terminal can run forever with no memory leaks.

Additional info:

The problem does not seem to be triggered by the user.  When I was using an X
application launched from gnome-terminal, it started and killed not only
gnome-terminal but the app I was using :(

Comment 1 Havoc Pennington 2002-12-16 18:30:53 UTC
All Xft apps (GTK2 or Qt3) do this if you don't have RENDER extension 
for your X server.

Try the test fix packages at ftp://people.redhat.com/hp/testing/

Comment 2 Owen Taylor 2003-01-07 20:48:30 UTC

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

Comment 3 Red Hat Bugzilla 2006-02-21 18:50:21 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.


Note You need to log in before you can comment on or make changes to this bug.