Bug 15187 - Memleak / OOM condition
Summary: Memleak / OOM condition
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: xscreensaver
Version: 6.2
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Bill Nottingham
QA Contact:
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2000-08-02 22:58 UTC by Mike A. Harris
Modified: 2014-03-17 02:15 UTC (History)
1 user (show)

(edit)
Clone Of:
(edit)
Last Closed: 2000-08-02 22:58:15 UTC


Attachments (Terms of Use)

Description Mike A. Harris 2000-08-02 22:58:13 UTC
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
dynamically
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
running
out of control.  The screensaver in question is the "teevee" one which
simulates
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 23:03:17 UTC
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.