Potential resource leak
Reports potential resource leaks, such as unclosed files, SQL rows, HTTP response bodies, or other resources that implement io.Closer and require explicit closure.
Example:
Locating this inspection
- By ID
Can be used to locate inspection in e.g. Qodana configuration files, where you can quickly enable or disable it, or adjust its settings.
GoResourceLeak- Via Settings dialog
Path to the inspection settings via IntelliJ Platform IDE Settings dialog, when you need to adjust inspection settings directly from your IDE.
Inspection ID: GoResourceLeak
Inspection options
Here you can find the description of settings available for the Potential resource leak inspection, and the reference of their default values.
- Disable in tests
Option ID:
disableInTestsDefault value:
Selected
Excluded functions
- Import Path
Option ID:
excludedFunctions.myImportPathsDefault value:
None- Function Name
Option ID:
excludedFunctions.myFunctionNamesDefault value:
None
Excluded methods
- Import Path
Option ID:
excludedMethods.myImportPathsDefault value:
None- Receiver
Option ID:
excludedMethods.myReceiversDefault value:
None- Method Name
Option ID:
excludedMethods.myMethodNamesDefault value:
None
Excluded types
- Name
Option ID:
excludedTypesDefault value:
None
Suppressing Inspection
You can suppress this inspection by placing the following comment marker before the code fragment where you no longer want messages from this inspection to appear:
More detailed instructions as well as other ways and options that you have can be found in the product documentation:
Inspection Details | |
|---|---|
By default bundled with: |