-
Notifications
You must be signed in to change notification settings - Fork 764
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
Check for usages of PhysicalFileProvider in all repos for leaks #844
Comments
Or call Dispose... The Finalizer may be a good mitigation for components like ConfigurationBuilder. We should look into making HostingEnvironment implement IDisposable as the primary fix for aspnet/Mvc#7696. |
Did a search on Universe repo's submodules:
Entropy:
|
Might be unimportant if we get it work correctly, but not all repos call |
Closing this. If we measure any issues, we'll fix them in the particular use location. |
Related to issue: aspnet/Mvc#7696
Repos where we instantiate the PhysicalFileProvider currently:
Repro:
You should see the memory increasing rapidly when you run the below app. Un-comment the line which uses the finalizer to see the memory usage being stable.
cc @Tratcher
The text was updated successfully, but these errors were encountered: