Bug 507431 - S/Lang stack / memory leaks
Summary: S/Lang stack / memory leaks
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: rgmanager
Version: 5.4
Hardware: All
OS: Linux
Target Milestone: rc
: ---
Assignee: Lon Hohberger
QA Contact: Cluster QE
Depends On:
TreeView+ depends on / blocked
Reported: 2009-06-22 18:28 UTC by Lon Hohberger
Modified: 2016-04-26 14:29 UTC (History)
2 users (show)

Fixed In Version: rgmanager-2.0.52-1.9
Doc Type: Bug Fix
Doc Text:
Clone Of: 507430
Last Closed: 2010-03-30 08:49:26 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2010:0280 0 normal SHIPPED_LIVE rgmanager bug fix and enhancement update 2010-03-29 13:59:11 UTC

Description Lon Hohberger 2009-06-22 18:28:12 UTC
Description of problem:

During event processing, an error in the S/Lang code can produce unwanted S/Lang stack leaks.  This can be fixed a number of ways, for example, purging the stack at the end of each run.  However, the correct fix is to not leak the variables in the first place.

After several hundred events are handled, the S/Lang stack can fill up, requiring a retry of the service operation.  On failover, this could result in a service not running if central_processing is enabled.

Normally, however, it's during a user operation, requiring a retry of that operation.

Additionally, a duplicated buffer when pushing service properties on to the stack was getting leaked.

Comment 6 Lon Hohberger 2009-09-28 15:44:01 UTC
Those commits are obsolete; I will have new ones momentarily.

Comment 12 errata-xmlrpc 2010-03-30 08:49:26 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.


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