https://github.com/operator-framework/operator-registry/pull/82 This may have addressed the issue, as there were several fixes in grpc-go that claim to fix leaks. We do not currently have a reproducer for the memory leak, however.
verified this bug first, will keep an eye on this. Can't reproduce this bug for now.
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://access.redhat.com/errata/RHBA-2019:2922