On Sat, 5 Dec 2020 00:35:27 GMT, Lin Zang wrote:
>> when use SA JMap dump commands, such as "jhsdb jmap --binaryheap" or "dump
>> heap" with "jhsdb clhsdb", it keep printing "dumpStack: not java Thread.".
>> Skip non-java thread stack dump to avoid printing the message.
>
> Lin Zang has updated
On Sat, 5 Dec 2020 01:46:31 GMT, Dan Smith wrote:
> Integration of [JEP 390](https://bugs.openjdk.java.net/browse/JDK-8249100).
>
> Development has been broken into 5 tasks, each with its own JBS issue:
> - Deprecate wrapper class constructors for removal
> - Revise "value-based class" & apply t
On Fri, 4 Dec 2020 22:38:24 GMT, Mandy Chung wrote:
>> This patch replaces some uses of `Reference::get` to `Reference::refersTo`
>> to avoid keeping a referent strongly reachable that could cause unnecessary
>> delay in collecting such object. I only made change in some but not all
>> class
Integration of JEP 390, addressing the following issues:
8252180: [JEP 390] Deprecate wrapper class constructors for removal
8254047: [JEP 390] Revise "value-based class" & apply to wrappers
8252181: [JEP 390] Define & apply annotation jdk.internal.ValueBased
8252183: [JEP 390] Add 'lint' warning
On Fri, 4 Dec 2020 19:39:58 GMT, Chris Plummer wrote:
>> Lin Zang has updated the pull request incrementally with one additional
>> commit since the last revision:
>>
>> remove deadcode of println instead of change in HeapHprofBinWriter
>
> Marked as reviewed by cjplummer (Reviewer).
@plumme
> when use SA JMap dump commands, such as "jhsdb jmap --binaryheap" or "dump
> heap" with "jhsdb clhsdb", it keep printing "dumpStack: not java Thread.".
> Skip non-java thread stack dump to avoid printing the message.
Lin Zang has updated the pull request incrementally with one additional commi
On Thu, 3 Dec 2020 12:06:23 GMT, Lin Zang wrote:
> when use SA JMap dump commands, such as "jhsdb jmap --binaryheap" or "dump
> heap" with "jhsdb clhsdb", it keep printing "dumpStack: not java Thread.".
> Skip non-java thread stack dump to avoid printing the message.
Marked as reviewed by phh
> This patch replaces some uses of `Reference::get` to `Reference::refersTo` to
> avoid keeping a referent strongly reachable that could cause unnecessary
> delay in collecting such object. I only made change in some but not all
> classes in core libraries when working with Kim on `Reference::
On Fri, 4 Dec 2020 20:14:13 GMT, Peter Levart wrote:
>> Good point on checking k != null. A cleaner check:
>>
>> // then check for equality if the referent is not cleared
>> Object k = e.get();
>> return k != null || key.equals(k);
>
> You meant: `return k != null && key.
On Fri, 4 Dec 2020 21:01:13 GMT, Chris Plummer wrote:
>> This PR replaces the withdrawn PR #1348. This PR tries to fix the underlying
>> problem, rather than fix the tests.
>>
>> The problem is that a number of JDI tests create objects on the debugger
>> side with calls to `newInstance()`. How
On Thu, 3 Dec 2020 12:55:04 GMT, Per Liden wrote:
> This PR replaces the withdrawn PR #1348. This PR tries to fix the underlying
> problem, rather than fix the tests.
>
> The problem is that a number of JDI tests create objects on the debugger side
> with calls to `newInstance()`. However, on
On Fri, 4 Dec 2020 20:16:14 GMT, Mandy Chung wrote:
>> src/java.management/share/classes/com/sun/jmx/mbeanserver/WeakIdentityHashMap.java
>> line 127:
>>
>>> 125: T got = get();
>>> 126: return got != null && wr.refersTo(got);
>>> 127: }
>>
>> Here you could pre
On Thu, 3 Dec 2020 12:55:04 GMT, Per Liden wrote:
> This PR replaces the withdrawn PR #1348. This PR tries to fix the underlying
> problem, rather than fix the tests.
>
> The problem is that a number of JDI tests create objects on the debugger side
> with calls to `newInstance()`. However, on
On Fri, 4 Dec 2020 20:05:23 GMT, Kevin Rushforth wrote:
>> This patch replaces some uses of `Reference::get` to `Reference::refersTo`
>> to avoid keeping a referent strongly reachable that could cause unnecessary
>> delay in collecting such object. I only made change in some but not all
>> c
On Fri, 4 Dec 2020 19:47:17 GMT, Peter Levart wrote:
>> This patch replaces some uses of `Reference::get` to `Reference::refersTo`
>> to avoid keeping a referent strongly reachable that could cause unnecessary
>> delay in collecting such object. I only made change in some but not all
>> clas
On Fri, 4 Dec 2020 20:09:01 GMT, Mandy Chung wrote:
>> src/java.base/share/classes/java/util/WeakHashMap.java line 293:
>>
>>> 291: // then checks for equality
>>> 292: Object k = e.get();
>>> 293: return key == k || key.equals(k);
>>
>> I think `key == k` is already cov
On Fri, 4 Dec 2020 18:12:36 GMT, Kim Barrett wrote:
>> This patch replaces some uses of `Reference::get` to `Reference::refersTo`
>> to avoid keeping a referent strongly reachable that could cause unnecessary
>> delay in collecting such object. I only made change in some but not all
>> class
On Thu, 3 Dec 2020 12:06:23 GMT, Lin Zang wrote:
> when use SA JMap dump commands, such as "jhsdb jmap --binaryheap" or "dump
> heap" with "jhsdb clhsdb", it keep printing "dumpStack: not java Thread.".
> Skip non-java thread stack dump to avoid printing the message.
Hi Lin,
It looks good.
Tha
On Thu, 3 Dec 2020 22:54:54 GMT, Mandy Chung wrote:
> This patch replaces some uses of `Reference::get` to `Reference::refersTo` to
> avoid keeping a referent strongly reachable that could cause unnecessary
> delay in collecting such object. I only made change in some but not all
> classes i
On Thu, 3 Dec 2020 22:54:54 GMT, Mandy Chung wrote:
> This patch replaces some uses of `Reference::get` to `Reference::refersTo` to
> avoid keeping a referent strongly reachable that could cause unnecessary
> delay in collecting such object. I only made change in some but not all
> classes i
On Thu, 3 Dec 2020 12:06:23 GMT, Lin Zang wrote:
> when use SA JMap dump commands, such as "jhsdb jmap --binaryheap" or "dump
> heap" with "jhsdb clhsdb", it keep printing "dumpStack: not java Thread.".
> Skip non-java thread stack dump to avoid printing the message.
Marked as reviewed by cjpl
On Thu, 3 Dec 2020 22:54:54 GMT, Mandy Chung wrote:
> This patch replaces some uses of `Reference::get` to `Reference::refersTo` to
> avoid keeping a referent strongly reachable that could cause unnecessary
> delay in collecting such object. I only made change in some but not all
> classes i
On Fri, 4 Dec 2020 09:19:23 GMT, Aleksey Shipilev wrote:
>> This patch replaces some uses of `Reference::get` to `Reference::refersTo`
>> to avoid keeping a referent strongly reachable that could cause unnecessary
>> delay in collecting such object. I only made change in some but not all
>>
On Fri, 4 Dec 2020 14:05:54 GMT, Erik Joelsson wrote:
>> My understanding of JEPs is that they should be viewed as living documents.
>> In this case, I think it's perfectly valid to update JEP 201 with additional
>> source code layout. Both for this and for the other missing dirs.
>
> Regarding
Imo this is good idea because it eliminates useless/voluminous output. It's a
behavioral change nonetheless, so it would be great for others to weigh in.
Code change is fine.
Thanks,
Paul
-Original Message-
From: serviceability-dev on behalf
of Lin Zang
Date: Thursday, December 3, 2
On Fri, 4 Dec 2020 14:03:08 GMT, Erik Joelsson wrote:
>>> And I can certainly move jdwp.spec to java.base instead.
>>
>> If jdwp.spec has to move to the src tree then src/java.se is probably the
>> most suitable home because Java SE specifies JDWP as an optional interface.
>> So nothing to do
On Fri, 4 Dec 2020 12:30:02 GMT, Alan Bateman wrote:
>> And I can certainly move jdwp.spec to java.base instead. That's the reason I
>> need input on this: All I know is that is definitely not the responsibility
>> of the Build Group to maintain that document, and I made my best guess at
>> wh
On Fri, 4 Dec 2020 11:38:51 GMT, Magnus Ihse Bursie wrote:
> And I can certainly move jdwp.spec to java.base instead.
If jdwp.spec has to move to the src tree then src/java.se is probably the most
suitable home because Java SE specifies JDWP as an optional interface. So
nothing to do with jav
On Fri, 4 Dec 2020 11:14:49 GMT, Alan Bateman wrote:
>> To facilitate review, here is a list on how the different directories under
>> make/data has moved.
>>
>> **To java.base:**
>> * blacklistedcertsconverter
>> * cacerts
>> * characterdata
>> * charsetmapping
>> * cldr
>> * currency
>> * lsr
On Fri, 4 Dec 2020 11:37:41 GMT, Magnus Ihse Bursie wrote:
>> Are you proposing any text or guidelines to be added to JEP 201 as part of
>> this?
>>
>> I think the location of jdwp.spec and its location in the build tree may
>> need to be looked at again. It was convenient to have it in the ma
On Thu, 3 Dec 2020 22:54:54 GMT, Mandy Chung wrote:
> This patch replaces some uses of `Reference::get` to `Reference::refersTo` to
> avoid keeping a referent strongly reachable that could cause unnecessary
> delay in collecting such object. I only made change in some but not all
> classes i
On Fri, 4 Dec 2020 10:29:48 GMT, Magnus Ihse Bursie wrote:
>> A lot (but not all) of the data in make/data is tied to a specific module.
>> For instance, the publicsuffixlist is used by java.base, and fontconfig by
>> java.desktop. (A few directories, like mainmanifest, is *actually* used by
>
On Thu, 3 Dec 2020 22:54:54 GMT, Mandy Chung wrote:
> This patch replaces some uses of `Reference::get` to `Reference::refersTo` to
> avoid keeping a referent strongly reachable that could cause unnecessary
> delay in collecting such object. I only made change in some but not all
> classes i
On Thu, 3 Dec 2020 23:44:20 GMT, Magnus Ihse Bursie wrote:
> A lot (but not all) of the data in make/data is tied to a specific module.
> For instance, the publicsuffixlist is used by java.base, and fontconfig by
> java.desktop. (A few directories, like mainmanifest, is *actually* used by
> ma
A lot (but not all) of the data in make/data is tied to a specific module. For
instance, the publicsuffixlist is used by java.base, and fontconfig by
java.desktop. (A few directories, like mainmanifest, is *actually* used by make
for the whole build.)
These data files should move to the module
On Thu, 3 Dec 2020 22:54:54 GMT, Mandy Chung wrote:
> This patch replaces some uses of `Reference::get` to `Reference::refersTo` to
> avoid keeping a referent strongly reachable that could cause unnecessary
> delay in collecting such object. I only made change in some but not all
> classes i
36 matches
Mail list logo
