Memory leak starting with version 3.0.12 #174
Comments
fpavageau
added a commit
to fpavageau/microgateway-plugins
that referenced
this issue
Apr 1, 2020
This is due to debug-js/debug#678. Fixes apigee#174
fpavageau
added a commit
to fpavageau/microgateway-plugins
that referenced
this issue
Apr 1, 2020
This is due to debug-js/debug#678. Fixes apigee#174
fpavageau
added a commit
to fpavageau/microgateway-plugins
that referenced
this issue
Apr 15, 2020
This is due to debug-js/debug#678. Fixes apigee#174
keyurkarnik
pushed a commit
that referenced
this issue
Apr 15, 2020
This is due to debug-js/debug#678. Fixes #174
keyurkarnik
pushed a commit
that referenced
this issue
Apr 15, 2020
This is due to debug-js/debug#678. Fixes #174
keyurkarnik
pushed a commit
that referenced
this issue
Apr 15, 2020
This is due to debug-js/debug#678. Fixes #174
keyurkarnik
pushed a commit
that referenced
this issue
Apr 15, 2020
This is due to debug-js/debug#678. Fixes #174
keyurkarnik
pushed a commit
that referenced
this issue
Apr 15, 2020
This is due to debug-js/debug#678. Fixes #174
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This refactoring between 3.0.11 and 3.0.12 introduced a memory leak, through the dynamic creation of
debuginstances. See debug-js/debug#678, and the possible fix currently waiting in debug-js/debug#740. This impacts apigee-internal/microgateway in version 3.1.0 and above.A possible fix is to locally cache the
debuginstance created for each component, instead of creating a new one for each request.It would also be possible to pass the existing
debuginstance instead of the component name as the parameter tocheckIfAuthorized(), but I guess it's less abstract.The text was updated successfully, but these errors were encountered: