RFR: 8333105: Shenandoah: Results of concurrent mark may be lost for degenerated cycle

[Y. Srinivas Ramakrishna]

On Wed, 29 May 2024 19:07:52 GMT, William Kemper <wkemper at openjdk.org> wrote:

> I'll try to trim it down. I shot myself in the foot after being confused by the original comment and deleting this check. Not having this check is not so serious for non-generational modes, but it is necessary to avoid heap corruption and crashes in the generational mode.

Could you, for the sake of completeness, document this specific _generational pathology_ in the ticket, because it might bring up some interesting thinking about the ways in which the two modes might interact wrt the existing structure of the state machine driving the progress of the collections in the two cases, and the presence of asynchronous interruptions of that normal state machine flow/transitions.

-------------

PR Comment: https://git.openjdk.org/jdk/pull/19434#issuecomment-2138158526