Bug 460381 - various valgrind reported startup memory leaks
Summary: various valgrind reported startup memory leaks
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: 389
Classification: Retired
Component: Directory Server
Version: 1.1.1
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Rich Megginson
QA Contact: Chandrasekar Kannan
URL:
Whiteboard: comment#1.review+nhosoi
Depends On:
Blocks: 249650 FDS112
TreeView+ depends on / blocked
 
Reported: 2008-08-27 21:28 UTC by Rich Megginson
Modified: 2015-01-04 23:33 UTC (History)
3 users (show)

Fixed In Version: 8.1
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-04-29 23:06:17 UTC


Attachments (Terms of Use)
diffs (8.04 KB, patch)
2008-08-27 21:28 UTC, Rich Megginson
no flags Details | Diff
cvs commit log (1.06 KB, text/plain)
2008-08-27 21:56 UTC, Rich Megginson
no flags Details
valgrind output (2.42 MB, text/plain)
2009-04-08 20:44 UTC, Jenny Severance
no flags Details

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


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