Skip to content
Navigation Menu
Sign in
Appearance settings
Platform
AI CODE CREATION
GitHub Copilot
Write better code with AI
GitHub Copilot app
Direct agents from issue to merge
MCP Registry
Integrate external tools
DEVELOPER WORKFLOWS
Actions
Automate any workflow
Codespaces
Instant dev environments
Issues
Plan and track work
Code Review
Manage code changes
Code Quality
Enforce quality at merge
APPLICATION SECURITY
GitHub Advanced Security
Find and fix vulnerabilities
Code security
Secure your code as you build
Secret protection
Stop leaks before they start
EXPLORE
Why GitHub
Documentation
Blog
Changelog
Marketplace
View all features
Solutions
BY COMPANY SIZE
Enterprises
Small and medium teams
Startups
Nonprofits
BY USE CASE
App Modernization
DevSecOps
DevOps
CI/CD
View all use cases
BY INDUSTRY
Healthcare
Financial services
Manufacturing
Government
View all industries
View all solutions
Resources
EXPLORE BY TOPIC
AI
Software Development
DevOps
Security
View all topics
EXPLORE BY TYPE
Customer stories
Events & webinars
Ebooks & reports
Business insights
GitHub Skills
SUPPORT & SERVICES
Documentation
Customer support
Community forum
Trust center
Partners
View all resources
Open Source
COMMUNITY
GitHub Sponsors
Fund open source developers
PROGRAMS
Security Lab
Maintainer Community
Accelerator
GitHub Stars
Archive Program
REPOSITORIES
Topics
Trending
Collections
Enterprise
ENTERPRISE SOLUTIONS
Enterprise platform
AI-powered developer platform
AVAILABLE ADD-ONS
GitHub Advanced Security
Enterprise-grade security features
Copilot for Business
Enterprise-grade AI features
Premium Support
Enterprise-grade 24/7 support
Pricing
Type
/
to search
Sign in
Sign up
Appearance settings
You signed in with another tab or window.
Reload
to refresh your session.
You signed out in another tab or window.
Reload
to refresh your session.
You switched accounts on another tab or window.
Reload
to refresh your session.
Dismiss alert
{{ message }}
Uh oh!
There was an error while loading.
Please reload this page
.
github
/
codeql
Public
Notifications
You must be signed in to change notification settings
Fork
2.1k
Star
9.9k
Code
Issues
998
Pull requests
447
Discussions
Actions
Projects
Security and quality
0
Insights
Additional navigation options
Code
Issues
Pull requests
Discussions
Actions
Projects
Security and quality
Insights
Files
Expand file tree
copilot/split-ruby-queries-configurations
Breadcrumbs
codeql
/
csharp
/
ql
/
src
/
Likely Bugs
/
StaticFieldWrittenByInstance.qhelp
Copy path
Blame
More file actions
Blame
More file actions
Latest commit
History
History
History
32 lines (27 loc) · 1.64 KB
copilot/split-ruby-queries-configurations
Breadcrumbs
codeql
/
csharp
/
ql
/
src
/
Likely Bugs
/
StaticFieldWrittenByInstance.qhelp
Copy path
Top
File metadata and controls
Code
Blame
32 lines (27 loc) · 1.64 KB
Raw
Copy raw file
Download raw file
Open symbols panel
Edit and raw actions
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
<!DOCTYPE qhelp PUBLIC
"-//Semmle//qhelp//EN"
"qhelp.dtd">
<qhelp>
<overview>
<p>Static fields represent the shared state of all instances of a class. It is therefore bad practice to modify this state
from any particular instance. Because static fields are shared between all instances of a class existing in all threads of a program,
one instance trying to read the field while another tries to write it can lead to race conditions and hence mean the class is not
thread safe. It also decreases readability as most developers expect instance methods to only affect the instance state and
static methods to only affect the static state.</p>
</overview>
<recommendation>
<p>It is important to evaluate the situation carefully before implementing a fix for an alert of this rule. Perhaps the field
is erroneously declared static, and should in fact be an instance field; if so, then remove the static modifier from the field.
If the field genuinely has to be static, evaluate the assumptions behind the code. Does it really have to be modified directly
in an instance method? It could be helpful to wrap the accesses to the field in static methods, so that any concerns about
synchronization can be addressed while avoiding code duplication.</p>
</recommendation>
<example>
<p>In this example the field called "name" has been mistakenly declared static. Attempting to rename a person will actually modify
the static name field and affect all people.</p>
<sample src="StaticFieldWrittenByInstance.cs" />
</example>
<references>
<li>MSDN, C# Reference, <a href="http://msdn.microsoft.com/en-us/library/98f28cdx(v=vs.71).aspx">static</a>.</li>
</references>
</qhelp>
You can’t perform that action at this time.