On Fri, 2 Jul 2021 12:05:35 GMT, Lin Zang wrote:
> This PR rewrite the implementation of the HeapHprofBinWriter, which could
> simplify the logic of current implementation.
> please see detail description at
> https://bugs.openjdk.java.net/browse/JDK-8269685.
This pull request has now been
Follow-up change to JDK-8232442, augmentations to javac's Xlint:serial checking
are out for review (#5709) and various management libraries would need some
changes to pass under the expanded checks.
The changes are to suppress warnings where non-transient fields in serializable
types are not
On Sat, 25 Sep 2021 10:51:12 GMT, Andrey Turbanov
wrote:
> There are a few places in code, where manual `for` loop is used with Iterator
> to iterate over Collection.
> Instead of manual `for` cycles, it's preferred to use enhanced-for cycle
> instead: it's less verbose, makes code easier to
On Fri, 24 Sep 2021 07:30:02 GMT, Andrey Turbanov
wrote:
> There are few places in code where manual `for` loop is used with Iterator to
> iterate over Collection or Array.
> Instead of manual `for` cycles it's preferred to use enhanced-for cycle
> instead: it's less verbose, makes code
On Mon, 20 Sep 2021 08:15:13 GMT, Andrey Turbanov
wrote:
> There are few places in code where manual `for` loop is used with Iterator to
> iterate over Collection or Array.
> Instead of manual `for` cycles it's preferred to use enhanced-for cycle
> instead: it's less verbose, makes code
There are few places in code where manual `for` loop is used with Iterator to
iterate over Collection or Array.
Instead of manual `for` cycles it's preferred to use enhanced-for cycle
instead: it's less verbose, makes code easier to read and it's less error-prone.
It doesn't have any performance
On Sat, 25 Sep 2021 14:22:28 GMT, Markus Grönlund wrote:
>> Greetings,
>>
>> Object.finalize() was deprecated in JDK9. There is an ongoing effort to
>> replace and mitigate Object.finalize() uses in the JDK libraries; please see
>> https://bugs.openjdk.java.net/browse/JDK-8253568 for more
On Mon, 27 Sep 2021 13:06:57 GMT, Per Liden wrote:
>> Lin Zang has updated the pull request incrementally with one additional
>> commit since the last revision:
>>
>> remove redundant empty line
>
> src/hotspot/share/services/heapDumper.cpp line 1601:
>
>> 1599: void
> The root cause for crash in ZGC is that the JNIHandles are processed before
> object iteration. And ZGC would update the JNIHandles at object iteration
> with read barrier. So the crash is cause by accessing the invalid address
> which can be dummy info after zgc, and hence crash.
>
> The
On Mon, 27 Sep 2021 12:02:53 GMT, Lin Zang wrote:
>> The root cause for crash in ZGC is that the JNIHandles are processed before
>> object iteration. And ZGC would update the JNIHandles at object iteration
>> with read barrier. So the crash is cause by accessing the invalid address
>> which
On Mon, 27 Sep 2021 01:00:18 GMT, Joe Darcy wrote:
> This is an initial PR for expanded lint warnings done under two bugs:
>
> 8202056: Expand serial warning to check for bad overloads of serial-related
> methods and ineffectual fields
> 8160675: Issue lint warning for non-serializable
> The root cause for crash in ZGC is that the JNIHandles are processed before
> object iteration. And ZGC would update the JNIHandles at object iteration
> with read barrier. So the crash is cause by accessing the invalid address
> which can be dummy info after zgc, and hence crash.
>
> The
> The root cause for crash in ZGC is that the JNIHandles are processed before
> object iteration. And ZGC would update the JNIHandles at object iteration
> with read barrier. So the crash is cause by accessing the invalid address
> which can be dummy info after zgc, and hence crash.
>
> The
On Mon, 27 Sep 2021 09:39:59 GMT, Per Liden wrote:
> > The root cause for crash in ZGC is that the JNIHandles are processed before
> > object iteration. And ZGC would update the JNIHandles at object iteration
> > with read barrier. So the crash is cause by accessing the invalid address
> >
On Sun, 26 Sep 2021 08:02:33 GMT, Lin Zang wrote:
>> The root cause for crash in ZGC is that the JNIHandles are processed before
>> object iteration. And ZGC would update the JNIHandles at object iteration
>> with read barrier. So the crash is cause by accessing the invalid address
>> which
This is an initial PR for expanded lint warnings done under two bugs:
8202056: Expand serial warning to check for bad overloads of serial-related
methods and ineffectual fields
8160675: Issue lint warning for non-serializable non-transient instance fields
in serializable type
to get feedback
On Fri, 24 Sep 2021 09:01:28 GMT, Andrey Turbanov
wrote:
>> src/jdk.jcmd/share/classes/sun/tools/jstat/OptionFormat.java line 81:
>>
>>> 79:
>>> 80: for (Iterator i = children.iterator();
>>> i.hasNext(); /* empty */) {
>>> 81: OptionFormat o = i.next();
>>
>> Why did
17 matches
Mail list logo
