On Fri, 29 Sep 2023 19:21:14 GMT, Alex Menkov wrote:
>> The change fixes 2 issues in hprof test library.
>> The issue were discovered during test development (logging values of dumped
>> heap objects).
>> - JavaValueArray.elementSize cannot determine size of the array elements and
>> throws Run
On Thu, 28 Sep 2023 21:04:58 GMT, Leonid Mesnik wrote:
>> The test fails because ThreadDeath is raised during class
>> jdk.internal.misc.VirtualThreads initialization. The proposed fix is to
>> pre-initialize this step to avoid such failures. See more details in the bug.
>> I reproduced the ori
On Fri, 29 Sep 2023 19:21:14 GMT, Alex Menkov wrote:
>> The change fixes 2 issues in hprof test library.
>> The issue were discovered during test development (logging values of dumped
>> heap objects).
>> - JavaValueArray.elementSize cannot determine size of the array elements and
>> throws Run
On Thu, 28 Sep 2023 16:44:26 GMT, Varada M wrote:
>> Similar issue [JDK-8303549](https://bugs.openjdk.org/browse/JDK-8303549)
>> where AttachCurrentThread is failing on AIX due to stack size issue.
>> Test cases:
>> runtime/jni/terminatedThread/TestTerminatedThread.java
>> vmTestbase/nsk/jvmti
On Fri, 29 Sep 2023 03:18:48 GMT, Leonid Mesnik wrote:
>> Alex Menkov has updated the pull request incrementally with one additional
>> commit since the last revision:
>>
>> Added bug tag to the test
>
> test/lib-test/jdk/test/lib/hprof/HprofTest.java line 46:
>
>> 44: * @bug 8316778
>> 45:
> The change fixes 2 issues in hprof test library.
> The issue were discovered during test development (logging values of dumped
> heap objects).
> - JavaValueArray.elementSize cannot determine size of the array elements and
> throws RuntimeException: invalid array element type
> - JavaObject.toS
> The main.wrapper was the first name for jtreg test thread factory plugin.
> However, during integration of this feature in jtreg it was decided to use
> test.thread.factory name. So this fix just renames "main.wrapper" property to
> "test.thread.factory" so it is more compliant with jtreg nam
On 9/28/23 10:38 PM, Alan Bateman wrote:
On 28/09/2023 21:42, daniel.daughe...@oracle.com wrote:
java.lang.instrument is owned by the Serviceability Team so I'm
redirecting this
message to that alias...
This doesn't look like a JDK issue, instead it looks like
|com.github.jelmerk.ObjectS
On Fri, 29 Sep 2023 02:56:07 GMT, David Holmes wrote:
> > > Hmmm okay - it seems fragile to have a psuedo-destructor in release().
> >
> >
> > I don't know what this comment means.
>
> Object lifetimes should be well managed such that you can't use an object
> after it has been "destroyed". M
On Mon, 25 Sep 2023 16:16:51 GMT, Roman Kennke wrote:
> The SA can run concurrently with Java threads, SA code that inspects locking
> state should be able to deal with that. On the other hand, the particular
> code is only used in printing routine and is not expected to be precise. When
> res
On Thu, 28 Sep 2023 09:11:12 GMT, Roman Kennke wrote:
>> The SA can run concurrently with Java threads, SA code that inspects locking
>> state should be able to deal with that. On the other hand, the particular
>> code is only used in printing routine and is not expected to be precise.
>> When
11 matches
Mail list logo
