Cause: gssproxy leaked memory on a per-call basis
Consequence: OOM killer
Fix: free the memory instead
Result: gssproxy should not leak enough to trigger the OOM killer
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 (gssproxy bug fix and enhancement update), 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://access.redhat.com/errata/RHBA-2021:2329
Created attachment 1755784 [details] recoge_datos_gssproxy.log