[windows][cws][wkint-494] fix long, slow memory leak in CWS due to missed notifi… #25493
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
…cations.
Change file and registry cache to (configurable size) LRU. Prevents missing messages from causing runaway memory leak.
While it won't prevent the messages from being lost, puts an upper bound on our memory consumption and prevents the leak.
Motivation
Additional Notes
Possible Drawbacks / Trade-offs
There is some possibility that using an LRU cache, if not sized properly, will cause us to miss additional messages
because the filename was prematurely expired from the cache.
Describe how to test/QA your changes
Run it in the wkit load environment.