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

OutOfMemory errors after upgrading to 10.0.0 #103

Open
andidev opened this issue Oct 15, 2024 · 0 comments
Open

OutOfMemory errors after upgrading to 10.0.0 #103

andidev opened this issue Oct 15, 2024 · 0 comments

Comments

@andidev
Copy link

andidev commented Oct 15, 2024

We get OutOfMemory errors on our aws lambda server after upgrading from 8.1.1 to 10.0.0.
It seem to happen slowly and we use a lot the maxAge and set it usually to 2 seconds.
My feeling is that this change has caused it to start happening: #94

What maybe happens is that the setTimeout fails to clean cache since it sometimes will run when lambda has finished.
But this is just guessing.
How did the implementation change? Any clues here?
Was old dependency map-age-cleaner managing outdated cached values differently?

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

1 participant