Bug 460554 - gnome-terminal memory leak
Summary: gnome-terminal memory leak
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: gnome-terminal
Version: 5.3
Hardware: All
OS: Linux
high
medium
Target Milestone: rc
: ---
Assignee: Behdad Esfahbod
QA Contact: desktop-bugs@redhat.com
URL:
Whiteboard:
Depends On: 460553
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-08-28 15:47 UTC by Adam Stokes
Modified: 2018-10-19 21:05 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-08-25 15:52:37 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Adam Stokes 2008-08-28 15:47:16 UTC
+++ This bug was initially created as a clone of Bug #460553 +++

Description of problem:
When opening several terminals (or several tabs) memory is not released once terminal is closed by parent gnome-terminal process

Version-Release number of selected component (if applicable):
2.4.x-2.7.x

How reproducible:
100%

Steps to Reproduce:
1. Open 2 terminals or more
2. Open 2 terminals on second terminal open several tabs
3.
  
Actual results:
Memory consumed and not released

Expected results:
no leak

Additional info:
Patches from this bug made it into later version of gnome
http://bugzilla.gnome.org/show_bug.cgi?id=160993

Thanks

Comment 2 Behdad Esfahbod 2008-09-02 18:31:44 UTC
I need to see a specific leak report before doing anything.  A verbal "memory is not released" is worth nothing as far as fixing the code is concerned.  Show me a valgrind leak report.  Ain't gonna fix something not broken.  Definitely not for RHEL.

Comment 5 RHEL Program Management 2009-03-26 17:27:50 UTC
This request was evaluated by Red Hat Product Management for
inclusion, but this component is not scheduled to be updated in
the current Red Hat Enterprise Linux release. If you would like
this request to be reviewed for the next minor release, ask your
support representative to set the next rhel-x.y flag to "?".


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