On Fri, 28 Jan 2022 07:46:40 GMT, Chris Plummer wrote:
>> This test is failing in the loom repo when using -Xcomp. The reason is
>> because loom introduced doing a full GC in the codecache sweeper, which
>> causes the large array that the test allocates to be GC'd before the heap
>> dump is
On Fri, 28 Jan 2022 07:46:40 GMT, Chris Plummer wrote:
>> This test is failing in the loom repo when using -Xcomp. The reason is
>> because loom introduced doing a full GC in the codecache sweeper, which
>> causes the large array that the test allocates to be GC'd before the heap
>> dump is
On Fri, 28 Jan 2022 06:08:55 GMT, Alan Bateman wrote:
>> Chris Plummer has updated the pull request incrementally with one additional
>> commit since the last revision:
>>
>> Use Reference.reachabilityFence() instead of static field.
>
>
On Fri, 28 Jan 2022 07:43:45 GMT, Chris Plummer wrote:
>> This test is failing in the loom repo when using -Xcomp. The reason is
>> because loom introduced doing a full GC in the codecache sweeper, which
>> causes the large array that the test allocates to be GC'd before the heap
>> dump is
> This test is failing in the loom repo when using -Xcomp. The reason is
> because loom introduced doing a full GC in the codecache sweeper, which
> causes the large array that the test allocates to be GC'd before the heap
> dump is done. The fix is to make the large array static rather than a
On Wed, 26 Jan 2022 20:03:21 GMT, Chris Plummer wrote:
> This test is failing in the loom repo when using -Xcomp. The reason is
> because loom introduced doing a full GC in the codecache sweeper, which
> causes the large array that the test allocates to be GC'd before the heap
> dump is done.
This test is failing in the loom repo when using -Xcomp. The reason is because
loom introduced doing a full GC in the codecache sweeper, which causes the
large array that the test allocates to be GC'd before the heap dump is done.
The fix is to make the large array static rather than a local
