-
-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Memory leak #134
Comments
|
I looked at your code briefly, but it's hard to follow where you're using the cache between the modules. If you look at 11.1.2...11.2.0 the only difference that could cause your behavioral change is making 'has()' public, which historically is known to be a problem if anything external makes an assumption on the boolean it returns without considering lazy expiration. 11.1.2 to 11.2.0 exposes 'has()' and exports the class. |
in 11.1.2 a statement was deleted which may be the cause of the leak if it leaves orphans in ram. it doesn't have test coverage. 11.1.1...11.1.2#diff-79389319fa7fe3ff2ff6e0d5c97a626b12d8a2c72323e8ad210f43c8f98b1d60L129 |
Fix has shipped in 11.2.1. |
Thanks for looking into! |
Hello, I want to draw your attention to a memory leak problem that's reported for maxmind I maintain: runk/node-maxmind#740
The only change between "good" and "bad" version of maxmind is the version upgrade of tiny-lru in September. Releases with notes: https://github.com/runk/node-maxmind/releases
Do you have any clues what this could be?
The text was updated successfully, but these errors were encountered: