You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This library isn't for volatile caches. If it was I would have written it in a way where every key knew how to populate itself and would just use the cache when RAM was available. Instead it is very much for persistant on-box caching.
If you are worried about memory limits, I'd recommend using performance.memory in Chrome and then doing things that are specific to your application on how to limit memory growth.
don't you think an unlimited hashmap growth may be also a security flaw?
What's happen if I intentionally make thousands of different requests and let the hashmap grows in the order of magnitude of hundreds of MB in little time?
Hi, what do you think about add this feature?
I mean just a simple way to control the cache grown.
The text was updated successfully, but these errors were encountered: