RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1343319 - Upstream TC 666 fails with valgrind memory leak warnings
Summary: Upstream TC 666 fails with valgrind memory leak warnings
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: pcp
Version: 7.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Frank Ch. Eigler
QA Contact: Miloš Prchlík
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-06-07 06:54 UTC by Miloš Prchlík
Modified: 2016-11-04 04:23 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-04 04:23:46 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:2344 0 normal SHIPPED_LIVE pcp bug fix and enhancement update 2016-11-03 13:46:51 UTC

Comment 3 Frank Ch. Eigler 2016-06-07 10:41:19 UTC 
Not one of the allocation sites identified in that valgrind report actually represents conceivably-leaky heap operations.  Each is for an object whose lifetime is associated with a stack frame and cannot leak.  There is no pmmgr bug there.

For valgrind to report this way is more likely to be a valgrind bug or some weird side-effect of shutdown due to a external kill -9 (?) from the test case driver.  Those suppression entries could go into the .../qa/valgrind-suppress* file to work around both.

It is false that this particular issue has been observed upstream already.  qa/666 has indeed been flakey, largely because of the time constraints imposed on it by nathans.  (It is a time-based asynchronous tool, and its own and downstream pm$client operations take an unpredictable amount of time.  By rushing the test, the subsidiary operations cannot always keep up.)  Pending improvements to qa/666 and pmmgr have been stuck in review (?) queues for many weeks.
Comment 4 Lukas Berk 2016-06-07 12:26:14 UTC 
(In reply to Frank Ch. Eigler from comment #3)
> Pending improvements to qa/666 and pmmgr have been stuck in review (?)
> queues for many weeks.

Hey Frank,  do those have a particular branch that I missed? I would be happy to take a look at the qa/666 improvements, but am unsure which specific commits are related to the change.
Comment 13 Miloš Prchlík 2016-08-20 11:09:02 UTC 
Verified for build pcp-3.11.3-3.el7.
Comment 15 errata-xmlrpc 2016-11-04 04:23:46 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.

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