Bug 1044219

Summary: fix memleak caused by 47347
Product: Red Hat Enterprise Linux 7 Reporter: Nathan Kinder <nkinder>
Component: 389-ds-baseAssignee: Rich Megginson <rmeggins>
Status: CLOSED CURRENTRELEASE QA Contact: Sankar Ramalingam <sramling>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.0CC: amsharma, jgalipea, nhosoi, rmeggins
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 389-ds-base-1.3.1.6-14.el7 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1044218 Environment:
Last Closed: 2014-06-13 13:22:00 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: 1044218    
Bug Blocks:    
Attachments:
Description Flags
valgrind.out
none
valgrind.out_1
none
valgrind.out_2 none

Description Nathan Kinder 2013-12-17 22:38:38 UTC 
+++ This bug was initially created as a clone of Bug #1044218 +++

This bug is created as a clone of upstream ticket:
https://fedorahosted.org/389/ticket/47623

==24307== 672 bytes in 4 blocks are definitely lost in loss record 1,264 of 1,456
==24307==    at 0x4A0577B: calloc (vg_replace_malloc.c:593)
==24307==    by 0x3A334238DC: PR_NewLock (ptsynch.c:142)
==24307==    by 0x4CAA8D0: pagedresults_parse_control_value (pagedresults.c:134)
==24307==    by 0x4CA825B: op_shared_search (opshared.c:464)
==24307==    by 0x42E515: do_search (search.c:355)
==24307==    by 0x414B63: connection_dispatch_operation (connection.c:622)
==24307==    by 0x416469: connection_threadmain (connection.c:2339)
==24307==    by 0x3A33429995: _pt_root (ptthread.c:204)
==24307==    by 0x3A244079D0: start_thread (pthread_create.c:301)
==24307==    by 0x3A23CE8B6C: clone (clone.S:115)
==24307==
Comment 1 Sankar Ramalingam 2013-12-20 10:28:01 UTC 
Can this be tested in QE environment?
Comment 2 Rich Megginson 2014-01-06 15:47:20 UTC 
(In reply to Sankar Ramalingam from comment #1)
> Can this be tested in QE environment?

If you can run the server with valgrind, and run the simple paged tests, then yes.
Comment 4 Amita Sharma 2014-01-23 11:59:50 UTC 
(In reply to Rich Megginson from comment #2)
> (In reply to Sankar Ramalingam from comment #1)
> > Can this be tested in QE environment?
> 
> If you can run the server with valgrind, and run the simple paged tests,
> then yes.

Hi Rich,
PFA for the valgrind output for simple paged tet execution. I think it does not report any memory leak, but just to be sure, Request you to please review the output once and I will move the bug to VERIFIED state.

Thanks & Regards,
Ami
Comment 5 Amita Sharma 2014-01-23 12:00:56 UTC 
Created attachment 854333 [details]
valgrind.out
Comment 6 Rich Megginson 2014-01-23 15:08:47 UTC 
These memory errors in the valgrind report are benign.

There are no leaks in the valgrind report.  Note that valgrind will _not_ report leaks until you shutdown the directory server.
Comment 7 Amita Sharma 2014-01-23 16:30:23 UTC 
Created attachment 854473 [details]
valgrind.out_1

So this is the valgrind output after shutting down the instance. PFA.
Comment 8 Rich Megginson 2014-01-23 16:37:10 UTC 
(In reply to Amita Sharma from comment #7)
> Created attachment 854473 [details]
> valgrind.out_1
> 
> So this is the valgrind output after shutting down the instance. PFA.

This is the valgrind report from the instance used for the simple paged test?
Comment 9 Amita Sharma 2014-01-24 06:32:49 UTC 
Created attachment 854784 [details]
valgrind.out_2

Hi Rich,
Sorry.. Some how file got truncated. PFA for final review.

Thanks,
Ami
Comment 10 Rich Megginson 2014-01-24 15:15:34 UTC 
valgrind looks good - ack
Comment 11 Amita Sharma 2014-01-27 05:49:10 UTC 
Thankyou Rich, Marking the bug as VERIFIED.
Comment 12 Ludek Smid 2014-06-13 13:22:00 UTC 
This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.