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
We use a structure unordered_lru_cache in a number of places for a performant cache. However, some of these instances, we do not set any limit in the number of cached objects. This could be a potential cause for "memory leak" reports. While not a memory leak, setting reasonable limits to these caches may resolve this long term growth, with no to little downside.
We use a structure unordered_lru_cache in a number of places for a performant cache. However, some of these instances, we do not set any limit in the number of cached objects. This could be a potential cause for "memory leak" reports. While not a memory leak, setting reasonable limits to these caches may resolve this long term growth, with no to little downside.
unordered_lru_cache usages
The text was updated successfully, but these errors were encountered: