ksh2020 has massive memory issues
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ksh (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
I have a complex ksh environment that I have built over 40 years and it's worked fine (with occasional tweaks) on most systems (SunOS, Solaris, BSD, HP-UX, AIX, NCR, many Linux versions). I just upgraded to kubuntu 20.04 and my 'xterm -ls' windows failed to open because the shell was crashing. I reverted to ksh93 and it worked again. Errors with ksh2020 were false reports of mismatched single or double quotes, among others. I stripped down my environment and managed to use 2020. But when I run some functions, it still blows up. I ran it with 'valgrind' (something that every single app should be run with before any release, especially a shell!) and it came up with hundreds of errors. Ksh93 only has a handful. Valgrind output is attached. My environment is probably too big to share with you but fixing all the glaring issues exposed by valgrind may resolve my problems. For now, I am back on ksh93.
information type: | Private Security → Public Security |
information type: | Public Security → Public |
affects: | canonical-identity-provider → ksh (Ubuntu) |
Chris, thanks for the report and Valgrind observations.
We have reverted ksh2020 back to ksh93u+, in Debian and Ubuntu with the latest version 2020.0. 0+really93u+ 20120801- 8 as of this writing available for Groovy Gorilla when you install the "ksh" package.
Could you pick up this version and let us know if you continue to run into problems? Happy to help resolve and/or bring them to the attention of folks who may be able to help you move forward.