Bug 2054239 - Test case failure: /CoreOS/ksh/Regression/memleaks (bash)
Summary: Test case failure: /CoreOS/ksh/Regression/memleaks (bash)
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: bash
Version: 9.0
Hardware: Unspecified
OS: Linux
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Siteshwar Vashisht
QA Contact: Karel Volný
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-02-14 13:59 UTC by Karel Volný
Modified: 2023-08-14 07:28 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-08-14 07:28:36 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-112171 0 None None None 2022-02-14 14:03:49 UTC

Description Karel Volný 2022-02-14 13:59:55 UTC
Filed from caserun https://tcms.engineering.redhat.com/run/422939/#caserun_27499964

Version-Release number of selected component (if applicable):
RHEL-9.0.0-20220127.4
bash-5.1.8-2.el9

Steps to Reproduce: 
run the first reproducer from /CoreOS/ksh/Regression/memleaks


Actual results: 
memory usage grows over time

Expected results:
memory usage doesn't grow


the reproducer script (ignore the shebang and feed to bash directly):

#!/usr/bin/ksh

function _hash {
        typeset w=([abc]=1 [def]=31534 [xyz]=42)
        print -u2 $w 2>&-
        # accessing the var will leak
}
function _array {
        typeset w=(1 31534 42)
        print -u2 $w 2>&-
        # unset w will prevent leak
}

print ${.sh.version}

pmap -x $$ |tail -1
for (( j=0; j<100; j++)); do
        for (( i=0; i<10000; i++)); do
               _hash
        done
        pmap -x $$ |tail -1
done
sleep 1

Comment 2 RHEL Program Management 2023-08-14 07:28:36 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.


Note You need to log in before you can comment on or make changes to this bug.