Skip to content
This repository has been archived by the owner on Mar 17, 2022. It is now read-only.

Leaking memory #8

Closed
kilokeith opened this issue May 8, 2013 · 2 comments
Closed

Leaking memory #8

kilokeith opened this issue May 8, 2013 · 2 comments

Comments

@kilokeith
Copy link

Just a heads up: I can't pinpoint exactly there this is happening, but in production on high traffic sites the cache is bleeding memory. Even with a small max(10-99), and small objects. I'm still looking into this issue.

@isaacs
Copy link
Owner

isaacs commented May 8, 2013

Why do you say async-cache is leaking memory?

Without many more details, I'm afraid this is just not an issue I can take any action on, so I'm closing it. I'll reopen if you have more details.

@isaacs isaacs closed this as completed May 8, 2013
@sunyonggang
Copy link

i am sorry, but i want to leave a message here. i use async-cache and meet memory leak, i use heapdump and solve my problem, it's not from async-cache, it's from my own code, i wrote one line code in the wrong position. may it be helpful, even it's two years from now 🏃

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

No branches or pull requests

3 participants