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

fix: memoize memory leak #5137

Merged
merged 1 commit into from Sep 27, 2023
Merged

fix: memoize memory leak #5137

merged 1 commit into from Sep 27, 2023

Conversation

TimBeyer
Copy link
Contributor

What this PR does / why we need it:
Memoize was using an object as a cache key whose identity kept changing. Thus it never returned a cache hit and kept storing new objects in cache. With this fixed, memory consumption becomes a lot more reasonable, plus the cache actually yields the desired performance benefits.

Which issue(s) this PR fixes:

Fixes #4638

Special notes for your reviewer:

Memoize was using an object as a cache key whose identity kept changing.
Thus it never returned a cache hit and kept storing new objects in cache.
With this fixed, memory consumption becomes a lot more reasonable, plus the cache actually yields the desired performance benefits.
Copy link
Contributor

@shumailxyz shumailxyz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Awesome 💯

@shumailxyz shumailxyz added this pull request to the merge queue Sep 27, 2023
Merged via the queue into main with commit 106eb72 Sep 27, 2023
41 checks passed
@shumailxyz shumailxyz deleted the fix/memoize-memory-leak branch September 27, 2023 10:55
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

Successfully merging this pull request may close these issues.

0.13: [Bug]: JavaScript heap out of memory on garden validate
2 participants