Skip to content
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 leaks #24

Closed
kilokeith opened this issue Oct 9, 2013 · 2 comments
Closed

Memory leaks #24

kilokeith opened this issue Oct 9, 2013 · 2 comments

Comments

@kilokeith
Copy link

I don't have anything other than anecdotal evidence to support this right now, but at high volume lru-cache leaks memory. It's not noticeable on most projects, but on my high volume sites I find that the servers are bleeding memory and require restarts every few hours. This is consistent with any caching modules that uses lru-cache as the underlying mechanism (mongoose-cache, async-cache, etc).

I'm still looking into this and trying to do memory profiling to determine what the bug is. I assume it has something to do with storing complex objects. But I just wanted to give a heads up in case anyone else plans on using this at large scale.

@isaacs
Copy link
Owner

isaacs commented Oct 9, 2013

When you have data or any way to reproduce, please share.

There are many high-volume sites using lru-cache at Joyent that don't appear to leak memory.

@isaacs isaacs closed this as completed Oct 9, 2013
@isaacs
Copy link
Owner

isaacs commented Oct 9, 2013

If you can reproduce it, the easiest way I know to track down the source of a memory leak is to run it on SmartOS, get a core dump with gcore, and then use ::findjsobjects in MDB to find out what is taking up the space.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants