Bug 15187 - Memleak / OOM condition
Memleak / OOM condition
Product: Red Hat Linux
Classification: Retired
Component: xscreensaver (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Bill Nottingham
Depends On:
  Show dependency treegraph
Reported: 2000-08-02 18:58 EDT by Mike A. Harris
Modified: 2014-03-16 22:15 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2000-08-02 18:58: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 Mike A. Harris 2000-08-02 18:58:13 EDT
I have GNOME's random screensaver feature enabled, and was switched to the
console while X was running random screensavers.  The system became very
slow while typing and my typing just plain stopped.  I switched to a
running copy
of "top" and saw that X was consuming 72Mb of RAM which is eons more than
it usually does.  I have a swap daemon set up which adds more swap
in the event of OOM condition nearing.  The daemon had added an extra 32Mb
swap file.  I checked running processes and saw the xscreensaver was
out of control.  The screensaver in question is the "teevee" one which
a television with the vertical hold off kilter and the screen wrapping
around, plus
interference fuzz, and similar.  While it is a cute screensaver, it would
have OOM'd
my machine had I not been cautious and running swapd.  ;o)

This may be exploitable I suppose.. I haven't looked into it though.
Comment 1 Bill Nottingham 2000-08-02 19:03:17 EDT
This is fixed in the current package.

From the xscreensaver changelog:

3.24:          Added -ignorant option to maze hack. 
               Fixed a bad leak in xteevee.

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