OutOfMemory errors after upgrading to 10.0.0 #103
Description
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?