Repository navigation
[mono][sgen] Add separate card mark function to be used with debug - #109698
BrzVlad merged 1 commit into
Conversation
Sorry, something went wrong.
|
Tagging subscribers to this area: @BrzVlad |
Sorry, something went wrong.
|
thank you for your great work. can it merge to release/9.0 ? |
Sorry, something went wrong.
| } | ||
| } | ||
|
|
||
| // Marks more cards so that it works with remset consistency debug checks |
There was a problem hiding this comment.
so is this only enabled in debug builds ?
Sorry, something went wrong.
There was a problem hiding this comment.
Sort of, only if certain debug flags are passed at runtime via env vars this is used to mark cards when copying objects. It is a conservative approach. It might be useful to backport since there are active crashes there that are not actionable and this PR should at least fix the use of some GC debugging features that might help investigate.
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.
|
/backport to release/9.0 |
Sorry, something went wrong.
|
Started backporting to release/9.0: https://github.com/dotnet/runtime/actions/runs/12081645709 |
Sorry, something went wrong.
|
/backport to release/8.0 |
Sorry, something went wrong.
|
Started backporting to release/8.0: https://github.com/dotnet/runtime/actions/runs/12081650337 |
Sorry, something went wrong.
thank you @BrzVlad |
Sorry, something went wrong.
|
/backport to release/9.0-staging |
Sorry, something went wrong.
|
Started backporting to release/9.0-staging: https://github.com/dotnet/runtime/actions/runs/12084256458 |
Sorry, something went wrong.
|
/backport to release/8.0-staging |
Sorry, something went wrong.
|
Started backporting to release/8.0-staging: https://github.com/dotnet/runtime/actions/runs/12084270546 |
Sorry, something went wrong.
…otnet#109698) 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.
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.