> When using -Xcomp, the liveness of some objects the test allocates is more
> precisely known, allowing the objects to be collected before the test
> expects. This became an issue in the loom repo because it has changes that
> result in a full GC when the codecache is swept. This is fixed by us
On Fri, 28 Jan 2022 07:46:01 GMT, Chris Plummer wrote:
>> When using -Xcomp, the liveness of some objects the test allocates is more
>> precisely known, allowing the objects to be collected before the test
>> expects. This became an issue in the loom repo because it has changes that
>> result
On Fri, 28 Jan 2022 07:49:42 GMT, Chris Plummer wrote:
>> When using -Xcomp, the liveness of some objects the test allocates is more
>> precisely known, allowing the objects to be collected before the test
>> expects. This became an issue in the loom repo because it has changes that
>> result
On Fri, 28 Jan 2022 07:49:42 GMT, Chris Plummer wrote:
>> When using -Xcomp, the liveness of some objects the test allocates is more
>> precisely known, allowing the objects to be collected before the test
>> expects. This became an issue in the loom repo because it has changes that
>> result
On Fri, 28 Jan 2022 07:49:42 GMT, Chris Plummer wrote:
>> When using -Xcomp, the liveness of some objects the test allocates is more
>> precisely known, allowing the objects to be collected before the test
>> expects. This became an issue in the loom repo because it has changes that
>> result
