We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I analyzed the ASP .NET Core code using the Svace static analyzer. It has found a HANDLE_LEAK category error with the following message:
new ReadableJsonConfigurationProvider() is not disposed at the end of the function
in method Execute(CommandContext context). Here's a source code:
Execute(CommandContext context)
aspnetcore/src/Tools/dotnet-user-secrets/src/Internal/SetCommand.cs
Lines 61 to 84 in d088530
An instance of the ReadableJsonConfigurationProvider class is created and can be disposed of.
ReadableJsonConfigurationProvider
What about adjusting this method to ensure proper disposal with a using statement? Like this:
using
using var provider = new ReadableJsonConfigurationProvider();
Found by Linux Verification Center (linuxtesting.org) with SVACE. Reporter: Aleksey Kolosov ([email protected]). Organization: [email protected]
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
I analyzed the ASP .NET Core code using the Svace static analyzer. It has found a HANDLE_LEAK category error with the following message:
new ReadableJsonConfigurationProvider() is not disposed at the end of the function
in method
Execute(CommandContext context)
. Here's a source code:aspnetcore/src/Tools/dotnet-user-secrets/src/Internal/SetCommand.cs
Lines 61 to 84 in d088530
An instance of the
ReadableJsonConfigurationProvider
class is created and can be disposed of.What about adjusting this method to ensure proper disposal with a
using
statement?Like this:
Found by Linux Verification Center (linuxtesting.org) with SVACE.
Reporter: Aleksey Kolosov ([email protected]).
Organization: [email protected]
The text was updated successfully, but these errors were encountered: