On Tue, 12 Jul 2022 14:28:18 GMT, Zhengyu Gu wrote:
> > It seems during test shutdown, ObjectFree events are being delivered after
> > JVMTI events have been disabled:
> > ```
> > nsk_jvmti_enableEvents(JVMTI_DISABLE, eventsCount, events, NULL);
> >
> > NSK_TRACE(jni->DeleteGlobalRef(de
On Tue, 12 Jul 2022 06:31:39 GMT, Chris Plummer wrote:
> It seems during test shutdown, ObjectFree events are being delivered after
> JVMTI events have been disabled:
>
> ```
> nsk_jvmti_enableEvents(JVMTI_DISABLE, eventsCount, events, NULL);
>
> NSK_TRACE(jni->DeleteGlobalRef(debugeeC
On Tue, 12 Jul 2022 06:31:39 GMT, Chris Plummer wrote:
> post_object_free
-
PR: https://git.openjdk.org/jdk/pull/9168
On Tue, 12 Jul 2022 01:44:28 GMT, Zhengyu Gu wrote:
>> Currently, jdi only check and process class unloading event when it detects
>> a new GC cycle.
>>
>> After [JDK-8212879](https://bugs.openjdk.org/browse/JDK-8212879), posting
>> class events can overlap with GC finish event, that results,
On Tue, 12 Jul 2022 01:44:28 GMT, Zhengyu Gu wrote:
>> Currently, jdi only check and process class unloading event when it detects
>> a new GC cycle.
>>
>> After [JDK-8212879](https://bugs.openjdk.org/browse/JDK-8212879), posting
>> class events can overlap with GC finish event, that results,
On Tue, 12 Jul 2022 01:44:28 GMT, Zhengyu Gu wrote:
>> Currently, jdi only check and process class unloading event when it detects
>> a new GC cycle.
>>
>> After [JDK-8212879](https://bugs.openjdk.org/browse/JDK-8212879), posting
>> class events can overlap with GC finish event, that results,
> Currently, jdi only check and process class unloading event when it detects a
> new GC cycle.
>
> After [JDK-8212879](https://bugs.openjdk.org/browse/JDK-8212879), posting
> class events can overlap with GC finish event, that results, sometimes, it
> only captures partial or even empty unload
