Thanks for your explanation!
We running an OCP 4.3 for about 14 hours and have a regression test round on it.
No memory leak found, LGTM, verify it.
Cluster version is 4.3.0-0.nightly-2019-11-21-122827
mac:~ jianzhang$ oc exec catalog-operator-6b49d676c7-5fv6j -- olm --version
OLM version: 0.13.0
git commit: ba10413e72cfe23724edc588ff25f36dfdbeb37e
mac:~ jianzhang$ oc adm top pods
NAME CPU(cores) MEMORY(bytes)
catalog-operator-6b49d676c7-5fv6j 6m 48Mi
olm-operator-c495ddf7c-jtx57 19m 83Mi
packageserver-754d4947cb-mwd95 1m 19Mi
packageserver-754d4947cb-n42gl 1m 20Mi
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.