Bug 74972 - Memory leak in gnome-terminal
Memory leak in gnome-terminal
Status: CLOSED CURRENTRELEASE
Product: Red Hat Linux
Classification: Retired
Component: vte (Show other bugs)
8.0
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Ray Strode [halfline]
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2002-10-03 05:08 EDT by Peter Klotz
Modified: 2007-04-18 12:47 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2004-11-09 14:03:33 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
Output of xdpyinfo (1.17 KB, application/octet-stream)
2002-10-18 11:37 EDT, Peter Klotz
no flags Details

  None (edit)
Description Peter Klotz 2002-10-03 05:08:37 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.1) Gecko/20020826

Description of problem:
After updating Red Hat 7.3 to 8.0 I am experiencing a massive memory leak in
gnome-terminal. rpm reports that gnome-terminal-2.0.1-5 is installed.

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


How reproducible:
Always

Steps to Reproduce:
1.Just start gnome-terminal via the Gnome menu and run a top inside.
2.Sort the displayed columns according to memory usage by pressing M.
3.Have a look at the gnome-terminal entry and wait a few seconds.
	

Additional info:
Comment 1 Ali-Reza Anghaie 2002-10-03 14:50:17 EDT
Potentially a dupe of 74748 .. Cheers, -Ali
Comment 2 Nalin Dahyabhai 2002-10-17 20:30:48 EDT
If you run "xdpyinfo", is RENDER one of the listed extensions?
Comment 3 Peter Klotz 2002-10-18 11:37:51 EDT
Created attachment 80945 [details]
Output of xdpyinfo
Comment 4 Peter Klotz 2002-10-18 11:40:17 EDT
No extension RENDER is listed.
Comment 5 Ray Strode [halfline] 2004-11-09 14:03:33 EST
This was fixed a couple of years ago.  Closing...

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