| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
When marking cards for a non-array object or a an element vt in an object, it is enough to mark a card for any address within that object/vt because they are always fully scanned. Cardtable consistency checks are not accounting for this detail and it is difficult to have it implemented. Instead, when having such debug flags enabled, we use an explicit approach where every single card is being marked.
|
@BrzVlad please take a look at the PR failures and merge when ready |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Backport of #109698 to release/9.0-staging
/cc @BrzVlad
Customer Impact
There are existing GC related crashes in the wild, that are currently impossible to investigate. A debug option that might assist this is MONO_GC_DEBUG=check-remset-consistency, however a customer reported that this option reports false positives. This PR fixes these false positives, hopefully assisting in the investigation of aforementioned GC crashes.
Regression
No.
Testing
Manual testing locally.
Risk
Low. This change has no impact unless a certain debug flag is passed, flag which is used for the sole purpose of tracking down GC crashes.