RFR(S): JDK-8143921 nsk/jdi/ObjectReference/waitingThreads/waitingthreads003 fails with JVMTI_ERROR_INVALID_CLASS
serguei.spitsyn at oracle.com
serguei.spitsyn at oracle.com
Tue Apr 19 16:42:32 UTC 2016
Hi Dmitry,
144 // Clazz become invalid since the time we get the class list
145 // Skip this entry
146 if (error == JVMTI_ERROR_INVALID_CLASS) {
147 continue;
148 }
149
I'd like to better understand the root cause of this issue.
Could you, please, give an idea why a class in this test becomes invalid?
Do you think there is a potential in this test for a class to get unloaded?
Or is it something about anonymous classes?
Thanks,
Serguei
On 4/19/16 06:56, Dmitry Samersoff wrote:
> Any reviewers?
>
> On 2016-04-13 19:24, Dmitry Samersoff wrote:
>> Everybody.
>>
>> Please review a small fix.
>>
>> http://cr.openjdk.java.net/~dsamersoff/JDK-8143921/webrev.01/
>>
>> I don't have a reproducer, so the fix is based on coredump analyzes.
>>
>> Tested with rbt
>>
>> -Dmitry
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.openjdk.java.net/pipermail/serviceability-dev/attachments/20160419/fa7b0ee8/attachment.html>
More information about the serviceability-dev
mailing list