Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 2601 - Enlightenment Memory Leaks
Enlightenment Memory Leaks
Product: Red Hat Linux
Classification: Retired
Component: distribution (Show other bugs)
i386 Linux
high Severity high
: ---
: ---
Assigned To: David Lawrence
Depends On:
  Show dependency treegraph
Reported: 1999-05-06 11:47 EDT by mxk
Modified: 2008-05-01 11:37 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 1999-06-04 11:25:15 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description mxk 1999-05-06 11:47:36 EDT
Under stock redhat 6.0, using gnome, the supplied
enlightenment binaries leak memory like a sieve with a hole
in it. I'm using all stock supplied packages, and gnome with
the marble 3d theme. It seems that when I change desktop
areas (goto left desktop or right, etc.) that the binary's
size grows, and it never seems to go down. gnomepager seems
to grow along with it. Restarting E helps, but doesn't
reduce gnomepager's size. This is REALLY annoying, as I need
to log in and out to fix the whole problem.
Comment 1 richardc 1999-06-03 09:00:59 EDT
I've noticed this as well.  Running Xvnc, under the gnome desktop,
the image grows massively every time I just select a menu.  Within a
matter of minutes, the resident image is so big, I have to shut down
and restart the server.  This does not happen under KDE.
Comment 2 Jay Turner 1999-06-04 11:25:59 EDT
We are aware of several GTK themes that have memory leaks.  Try
changing the GTK theme and see whether you still get the E memory
leak.  In the test lab we have not seen leaks from E alone, only  when
combined with leaky themes and applications.  Reopen the bug if you
are still having problems.

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