Bug 460381

Summary: various valgrind reported startup memory leaks
Product: [Retired] 389 Reporter: Rich Megginson <rmeggins>
Component: Directory ServerAssignee: Rich Megginson <rmeggins>
Status: CLOSED CURRENTRELEASE QA Contact: Chandrasekar Kannan <ckannan>
Severity: medium Docs Contact:
Priority: medium    
Version: 1.1.1CC: benl, jgalipea, nhosoi
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard: comment#1.review+nhosoi
Fixed In Version: 8.1 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-04-29 23:06:17 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 249650, 452721    
Attachments:
Description Flags
diffs
none
cvs commit log
none
valgrind output none

Description Rich Megginson 2008-08-27 21:28:20 UTC
These memory leaks are not serious, but they do create a lot of noise in valgrind.

Comment 1 Rich Megginson 2008-08-27 21:28:42 UTC
Created attachment 315152 [details]
diffs

Comment 2 Rich Megginson 2008-08-27 21:56:44 UTC
Created attachment 315155 [details]
cvs commit log

Comment 3 Jenny Severance 2009-04-01 17:06:57 UTC
can you please add how to verify - just start up the server through valgrind?  Attach valgind output for verification?  Thanks

Comment 4 Rich Megginson 2009-04-06 21:17:16 UTC
yes, just startup and shutdown

Comment 5 Jenny Severance 2009-04-08 20:44:09 UTC
attaching valgrind report for review - DS 8.1 - RHEL 4 - startup looks pretty quiet now - shutdown is a bit noisy though ..

Comment 6 Jenny Severance 2009-04-08 20:44:49 UTC
Created attachment 338798 [details]
valgrind output

Comment 7 Rich Megginson 2009-04-08 21:24:18 UTC
Still a lot of leaks reported during shutdown, but none that appear to be per-op or per-connection.  Verified.

Comment 8 Jenny Severance 2009-04-09 12:36:19 UTC
Thanks Rich.

Comment 9 Chandrasekar Kannan 2009-04-29 23:06:17 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.

http://rhn.redhat.com/errata/RHEA-2009-0455.html