Closed JohanBengtsson closed 4 years ago
Thanks, we'll take a look. Out of curiosity, are you actually using a proxy (via the HTTPS_PROXY
environment variable) or is it just the fact of importing https-proxy-agent
that triggers the memory leak?
Thanks for your reply!
It seems now that the memory leak has returned after a few days regardless of the workaround I stated about. Something is fishy here and I think we'll have to do some further intestigation. Will come back with more information in a couple of days!
After some more tests, we suspect the problem must lie somewhere else. Will close this now.
Background of issue
When updgrading to version
0.10.3
a few weeks ago, we've experienced extreme memory leaks in our Node application using this library. We've verified it's this exact version of mixpanel that causes the issue. More specifically we believe it's the updrade of the dependencyhttps-proxy-agent
to3.0.0
was the root cause, i.e. this commitTemporary workaround
We've solved this temporarily by locking
mixpanel
to0.10.2
and solving thehttps-proxy-agent
security vulnerability by resolving it to a secure version in ourpackage.json
:point_down:Questions
Can someone confirm whether our suspicions about a memory leak existing in version
0.10.3
of this library are correct? If yes, is there a maintainer that can get out patch for this?