Bug 1044218 - fix memleak caused by 47347
Summary: fix memleak caused by 47347
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: 389-ds-base
Version: 6.4
Hardware: All
OS: Linux
urgent
urgent
Target Milestone: rc
: ---
Assignee: Rich Megginson
QA Contact: Sankar Ramalingam
URL:
Whiteboard:
Depends On:
Blocks: 1044219 1061410 1071707 1094412
TreeView+ depends on / blocked
 
Reported: 2013-12-17 22:36 UTC by Nathan Kinder
Modified: 2020-09-13 20:52 UTC (History)
8 users (show)

Fixed In Version: 389-ds-base-1.2.11.15-34.el6
Doc Type: Bug Fix
Doc Text:
Previously, the size of the directory server constantly increased after search requests for a simple paged results were processed. The memory leak causing this bug has been fixed, and the server size no longer increases in the aforementioned scenario.
Clone Of:
: 1044219 (view as bug list)
Environment:
Last Closed: 2014-10-14 07:52:40 UTC
Target Upstream Version:

Attachments (Terms of Use)
valgrind.out (56.85 KB, text/plain)
2014-07-30 13:04 UTC, Viktor Ashirov 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Github 389ds 389-ds-base issues 960 0 None None None 2020-09-13 20:52:30 UTC
Red Hat Product Errata RHBA-2014:1385 0 normal SHIPPED_LIVE 389-ds-base bug fix and enhancement update 2014-10-14 01:27:42 UTC

Description Nathan Kinder 2013-12-17 22:36:49 UTC 
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 3 Amita Sharma 2014-06-05 07:05:04 UTC 
check https://bugzilla.redhat.com/show_bug.cgi?id=1044219 for steps
Comment 5 Viktor Ashirov 2014-07-30 13:04:57 UTC 
Created attachment 922568 [details]
valgrind.out

Output of valgrind running 389-ds-base-1.2.11.15-38.el6.x86_64
Comment 6 Viktor Ashirov 2014-07-30 13:13:54 UTC 
Hi Rich, 

I ran the simple paged tests under valgrind, looks like there are no mentions of pagedresults_parse_control_value in the valgrind log. Could you please review the output just to be sure there are no related leaks? And then I'll move the state of the bug to VERIFIED.

Thanks!
Comment 7 Noriko Hosoi 2014-07-30 16:33:11 UTC 
Hi Viktor,

I reviewed your valgrind output (Rich is on PTO this week).

The output contains just memories allocated for the server initialization.  So, very clean.  Thank you for your thorough testing!
Comment 8 Viktor Ashirov 2014-07-30 16:39:57 UTC 
Thank you, Noriko!

Marking this bug as VERIFIED.
Comment 9 errata-xmlrpc 2014-10-14 07:52:40 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2014-1385.html
Note You need to log in before you can comment on or make changes to this bug.