Skip to content

Navigation Menu

Explore
By company size
By use case
By industry
View all solutions
Topics
- AI
- DevOps
- Security
- Software Development
- View all
Explore
- GitHub Sponsors
  Fund open source developers
- The ReadME Project
  GitHub community articles
Repositories
- Enterprise platform
  AI-powered developer platform
Available add-ons
Pricing

Search code, repositories, users, issues, pull requests...

Search

Clear

Search syntax tips

Provide feedback

We read every piece of feedback, and take your input very seriously.

Include my email address so I can be contacted

Saved searches

Use saved searches to filter your results more quickly

Name

Query

To see all available qualifiers, see our documentation.

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

dotnet / runtime Public

Notifications You must be signed in to change notification settings
Fork 4.8k
Star 15.7k

Code
Issues 5k+
Pull requests 329
Discussions
Actions
Projects 6
Security
Insights

Additional navigation options

Code
Issues
Pull requests
Discussions
Actions
Projects
Security
Insights

Make GC stress usable with Libraries tests#103738

Merged

VSadov merged 11 commits intodotnet:maindotnet/runtime:mainfrom VSadov:gcstress01VSadov/runtime:gcstress01Copy head branch name to clipboard

Jul 3, 2024

+58-21

Conversation Commits11 (11)Checks Files changed

Commits

Commits on Jul 2, 2024

do not do just gen2 when GCSTRESS_INSTR_JIT is set
VSadov
committed
cleanups and disable GC stress while WFPF is in progress
VSadov
committed
Do not GC stress in preemptive mode
VSadov
committed
higher ratio of gen0
VSadov
committed
fix test
VSadov
committed
make s_nGcStressDisabled sequentially consistent for multiuthreaded use
VSadov
committed
just use a compiler fence, to not raise questions if ordering is important
VSadov
committed
make GCC happy and bring back m_bAcquired
VSadov
committed

Commits on Jul 3, 2024

workaround an unused variable warning
VSadov
committed
Apply suggestions from code review

VSadov
and
jkotas
authored
use more compiler-happy pattern when asserting on return value.
VSadov
committed

Footer

© 2025 GitHub, Inc.

Footer navigation

Terms
Privacy
Security
Status
Docs
Contact

You can’t perform that action at this time.