GCStress: instrumented instructions only force a GC once

[BruceForstall]

One possible limitation of GCStress today is that each instruction is instrumented and stressed only once. After GC is run on an instrumented instruction, that instrumented instruction is replaced by its original instruction, so it never triggers a GC again. This means if a hole exists at an instruction, but isn't triggered by the first run of the instruction, we will miss it. This was potentially the case with the JIT creating illegal byrefs, fixed by dotnet/coreclr#17524.

Possibly introduce a (super slow) mode where we don't replace the instrumented instructions by their original instructions, or not immediately. Or, periodically re-instrument functions.

[ghost]

Due to lack of recent activity, this issue has been marked as a candidate for backlog cleanup. It will be closed if no further activity occurs within 14 more days. Any new comment (by anyone, not necessarily the author) will undo this process.

This process is part of our issue cleanup automation.

[ghost]

This issue will now be closed since it had been marked no-recent-activity but received no further activity in the past 14 days. It is still possible to reopen or comment on the issue, but please note that the issue will be locked if it remains inactive for another 30 days.