RFR: 8331208: Memory stress test that checks OutOfMemoryError stack trace fails

[Doug Simon]

On Tue, 30 Apr 2024 05:54:53 GMT, David Holmes <dholmes at openjdk.org> wrote:

> So you are generalising (and seemingly simplifying) the notion of a "retryable allocation" so that internally an OOME can be ignored for a range of reasons. It seems a rather elaborate response to the test failure (especially when generating a stacktrace under OOM conditions could itself fail anyway), but I can see the general utility of expanding things this way. I really dislike the name `SandboxedOOMEMark` though - sorry - suggestions: `InternalOOMEMark`, `ScopedOOMEMark`, `ConfinedOOMEMark` ?

Aren't sandboxed, scoped and confined kind of all the same concept? I don't mind using a different name but want to better understand the specific objection to "sandboxed" first.

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

PR Comment: https://git.openjdk.org/jdk/pull/18925#issuecomment-2084528115