On Fri, 28 Jan 2022 15:37:59 GMT, Aleksey Shipilev wrote:
> Recent test regression after adding new cases in the test. Without compressed
> oops, ~1G elements `Object[]` array takes >8G of memory, which fails the
> test. The fix cuts it down to 512M when reference size is 8 bytes.
> Additional
On Fri, 28 Jan 2022 07:34:21 GMT, Chris Plummer wrote:
> The test does a "threadcontext -v -a", and from the following output
> determines the threadID of the SteadyStateThread:
>
> `Thread "SteadyStateThread" id=23 Address=0x01dc51749420`
>
> It then tries threadcontext on this id, but
On Sun, 30 Jan 2022 21:47:45 GMT, David Holmes wrote:
> That seems bizarre. If this is a dump from our Java launcher then there
> should be no other threads created before the one that loads the JVM.
Maybe they are invisible threads that Windows creates on thread launch that are
deleted soon a
On Fri, 28 Jan 2022 07:34:21 GMT, Chris Plummer wrote:
> The test does a "threadcontext -v -a", and from the following output
> determines the threadID of the SteadyStateThread:
>
> `Thread "SteadyStateThread" id=23 Address=0x01dc51749420`
>
> It then tries threadcontext on this id, but
On Mon, 31 Jan 2022 05:06:38 GMT, David Holmes wrote:
> It may be an old issue but if we're using the wrong/inappropriate thread id
> and that is what causes the current bug then it does seem very pertinent to
> this PR. For a single "session" it doesn't matter which is used but if you
> want
