Bug 2033337

Summary:	memleak when using PATH
Product:	Red Hat Enterprise Linux 9	Reporter:	Karel Volný <kvolny>
Component:	ksh	Assignee:	Vincent Mihalkovič <vmihalko>
Status:	CLOSED MIGRATED	QA Contact:	Karel Volný <kvolny>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	9.0	CC:	lzaoral
Target Milestone:	rc	Keywords:	MigratedToJIRA, Reopened
Target Release:	---
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-09-20 20:26:06 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Karel Volný 2021-12-16 14:52:10 UTC

one of the tests for memleaks had been passing with the previous version ksh-20120801-256.el9 but fails with the new ksh-1.0.0~beta.1-2.el9

Filed from caserun https://tcms.engineering.redhat.com/run/422031/#caserun_27370827

Version-Release number of selected component (if applicable):
RHEL-9.0.0-20211121.7

Steps to Reproduce: 
run the test /CoreOS/ksh/Regression/memleaks


Actual results: 
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
::   repr_PATH.sh
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::

:: [ 19:19:00 ] :: [   LOG    ] :: Running repr_PATH.sh
:: [ 19:19:00 ] :: [  BEGIN   ] :: Running the reproducer repr_PATH.sh :: actually running 'ksh93 repr_PATH.sh > repr.log'
:: [ 19:21:29 ] :: [   PASS   ] :: Running the reproducer repr_PATH.sh (Expected 0, got 0)
total kB           10112    5632    1088
...
total kB           15424   11008    6464
total kB           15488   11072    6528
:: [ 19:21:29 ] :: [   FAIL   ] :: Kbytes shall not grow beyond acceptable variation (Assert: "13092" should be >= "15488")


Expected results:
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
::   repr_PATH.sh
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::

:: [ 01:37:58 ] :: [   LOG    ] :: Running repr_PATH.sh
:: [ 01:37:58 ] :: [  BEGIN   ] :: Running the reproducer repr_PATH.sh :: actually running 'ksh93 repr_PATH.sh > repr.log'
:: [ 01:40:24 ] :: [   PASS   ] :: Running the reproducer repr_PATH.sh (Expected 0, got 0)
total kB           10560    5760    1216
...
total kB           10560    5760    1216
total kB           10560    5824    1280
:: [ 01:40:24 ] :: [   PASS   ] :: Kbytes shall not grow beyond acceptable variation (Assert: "10660" should be >= "10560")

Comment 2 RHEL Program Management 2023-06-16 07:29:09 UTC

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.

Comment 4 RHEL Program Management 2023-09-20 20:24:17 UTC

Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 5 RHEL Program Management 2023-09-20 20:26:06 UTC

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.