Bug 910995
| Summary: | Valgrind reports memleak in modify_update_last_modified_attr | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Jiri Pallich <jpallich> |
| Component: | 389-ds-base | Assignee: | Rich Megginson <rmeggins> |
| Status: | CLOSED ERRATA | QA Contact: | Sankar Ramalingam <sramling> |
| Severity: | high | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 6.4 | CC: | abienven, dpal, jgalipea, jrusnack, jwest, nhosoi, nkinder, pm-eus, rmeggins, tlavigne |
| Target Milestone: | rc | Keywords: | ZStream |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | 389-ds-base-1.2.11.15-12.el6_4 | Doc Type: | Bug Fix |
| Doc Text: |
Previously, the vagrind test suite reported recurring memory leaks in the modify_update_last_modified_attr() function. The size of the leaks averaged between 60-80 bytes per the modify call. In environments where modify operations were frequent, this caused significant problems. Now, memory leaks no longer occur in the modify_update_last_modified_attr() function
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-03-11 18:38:35 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: | 906005 | ||
| Bug Blocks: | |||
|
Description
Jiri Pallich
2013-02-14 07:29:41 UTC
[jrusnack@dstet ~]$ grep modify_update_last_modified_attr valgrind.out [jrusnack@dstet ~]$ echo $? 1 [jrusnack@dstet ~]$ rpm -qa | grep 389 389-ds-base-libs-1.2.11.15-12.el6_4.i686 389-ds-base-debuginfo-1.2.11.15-12.el6_4.i686 389-ds-base-1.2.11.15-12.el6_4.i686 [jrusnack@dstet ~]$ cat /etc/redhat-release Red Hat Enterprise Linux Server release 6.4 (Santiago) Verified. 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/RHSA-2013-0628.html |