Access to 'static' field locked on instance data
Reports access to non-constant static fields that are locked on either this or an instance field of this.
Locking a static field on instance data does not prevent the field from being modified by other instances, and thus may result in unexpected race conditions.
Example:
There is a quick-fix that allows ignoring static fields of specific types. You can manage those ignored types in the inspection options.
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.
AccessToStaticFieldLockedOnInstance- 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.
Use the inspection options to specify which classes used for static fields should be ignored.
Inspection options
Here you can find the description of settings available for the Access to 'static' field locked on instance data inspection, and the reference of their default values.
- Ignored classes
Default value:
Empty
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: |