- Sponsor
-
Notifications
You must be signed in to change notification settings - Fork 357
Permalink
Choose a base ref
{{ refName }}
default
Choose a head ref
{{ refName }}
default
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
base repository: isaacs/node-lru-cache
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v7.5.1
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
...
head repository: isaacs/node-lru-cache
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v7.5.2
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
- 3 commits
- 6 files changed
- 1 contributor
Commits on Apr 9, 2022
-
Configuration menu - View commit details
-
Copy full SHA for d169d84 - Browse repository at this point
Copy the full SHA d169d84View commit details -
Fix memory leak in unbounded storage case
Evictions were no being tracked properly when maxSize triggered an eviction. In the max-bound storage case, this wasn't so much of a problem, because the storage couldn't grow unbounded anyway. However, since size-evicted indexes were not being added to the `free` list, it would effectively reduce the available storage space, holding onto old entries and shortening the available storage area, which would result in fewer items being cached (except some that were cached indefinitely!) In the unbounded case, this was much worse. Because the storage array was unbounded, the cache effectively always remained in the initial "fill to completion" state, resulting in holding onto _every_ item forever, while thinking that the `calculatedSize` was being limited to `maxSize`! Pretty bad. (This will be back-ported to other 7.x versions as a patch.) Thanks to @moish83 for the report. Fix: #227
Configuration menu - View commit details
-
Copy full SHA for ffd8542 - Browse repository at this point
Copy the full SHA ffd8542View commit details -
Configuration menu - View commit details
-
Copy full SHA for 5c146c6 - Browse repository at this point
Copy the full SHA 5c146c6View commit details
There are no files selected for viewing
Large diffs are not rendered by default.