Skip to content
This repository has been archived by the owner on Jul 5, 2020. It is now read-only.

Memory leak with MemoryCache #554

Closed
cijothomas opened this issue May 10, 2017 · 1 comment
Closed

Memory leak with MemoryCache #554

cijothomas opened this issue May 10, 2017 · 1 comment
Labels
Milestone

Comments

@cijothomas
Copy link
Contributor

After PR #516 , there are multiple readers/writers to the MemoryCache - EventSource processing and DiagnosticListener processing. Its not fully understood, but there seems to be a huge memory leak and dumps show MemoryCache is the cause. The items count in cache never goes above the expected value, but their memory usage keeps increasing forever.

Replacing mem cache with own implementation is fixing this problem. Opening this GH issue to understand the issue better or to see if we can live with custom implementation.

@cijothomas
Copy link
Contributor Author

The issue was with DependencyTableStore creating new MemoryCache as a side effect during every Instance property access. This problem existed for months now, but was aggravated with 516, as it called Instance property for every callback.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants