On Fri, 28 Jan 2022 07:46:01 GMT, Chris Plummer wrote:
>> When using -Xcomp, the liveness of some objects the test allocates is more
>> precisely known, allowing the objects to be collected before the test
>> expects. This became an issue in the loom repo because it has changes that
>> result
> When using -Xcomp, the liveness of some objects the test allocates is more
> precisely known, allowing the objects to be collected before the test
> expects. This became an issue in the loom repo because it has changes that
> result in a full GC when the codecache is swept. This is fixed by
On Fri, 28 Jan 2022 06:08:55 GMT, Alan Bateman wrote:
>> Chris Plummer has updated the pull request incrementally with one additional
>> commit since the last revision:
>>
>> Use Reference.reachabilityFence() instead of static field.
>
>
On Fri, 28 Jan 2022 07:43:45 GMT, Chris Plummer wrote:
>> This test is failing in the loom repo when using -Xcomp. The reason is
>> because loom introduced doing a full GC in the codecache sweeper, which
>> causes the large array that the test allocates to be GC'd before the heap
>> dump is
> This test is failing in the loom repo when using -Xcomp. The reason is
> because loom introduced doing a full GC in the codecache sweeper, which
> causes the large array that the test allocates to be GC'd before the heap
> dump is done. The fix is to make the large array static rather than a
The test does a "threadcontext -v -a", and from the following output determines
the threadID of the SteadyStateThread:
`Thread "SteadyStateThread" id=23 Address=0x01dc51749420`
It then tries threadcontext on this id, but it fails:
+ threadcontext -v 23
Couldn't find thread 23
This
On Wed, 26 Jan 2022 20:03:21 GMT, Chris Plummer wrote:
> This test is failing in the loom repo when using -Xcomp. The reason is
> because loom introduced doing a full GC in the codecache sweeper, which
> causes the large array that the test allocates to be GC'd before the heap
> dump is done.
When using -Xcomp, the liveness of some objects the test allocates is more
precisely known, allowing the objects to be collected before the test expects.
This became an issue in the loom repo because it has changes that result in a
full GC when the codecache is swept. This is fixed by using
This test is failing in the loom repo when using -Xcomp. The reason is because
loom introduced doing a full GC in the codecache sweeper, which causes the
large array that the test allocates to be GC'd before the heap dump is done.
The fix is to make the large array static rather than a local
On Tue, 25 Jan 2022 22:07:37 GMT, Chris Plummer wrote:
> It's possible for an address to be in the codecache but not in any CodeBlob.
> Don't assert in this case.
>
> Also I ran into a couple of other asserts listed below. It looks like since
> dumping the threadcontext can result in using
On Wed, 26 Jan 2022 14:27:54 GMT, Kevin Walls wrote:
>> Chris Plummer has updated the pull request incrementally with one additional
>> commit since the last revision:
>>
>> Guard against invalid CodeBlobs that may throw exceptions.
>
>
> It's possible for an address to be in the codecache but not in any CodeBlob.
> Don't assert in this case.
>
> Also I ran into a couple of other asserts listed below. It looks like since
> dumping the threadcontext can result in using PointerFinder with fairly
> random addresses, it is doing
The discussion of CDS in the man pages need to be cleaned up and updated to
match the latest functionalities and intended usage.
For java.md:
- Reorganized the flow of the doc: Overview -> How to use -> How to create ->
Restrictions and notes. I think this will be easier to read.
- Added
On Thu, 27 Jan 2022 17:44:39 GMT, Roger Riggs wrote:
>> Kevin Walls has updated the pull request incrementally with one additional
>> commit since the last revision:
>>
>> Wildcard in object filter to permit proxies, in case other activity in
>> this JVM changes the nameing/numbering of
On Mon, 10 Jan 2022 11:17:12 GMT, Kevin Walls wrote:
>> Remove the use of Security Manager from jstatd.
>> Add use of an ObjectInputFilter to restrict RMI.
>>
>> Also we can undo the property-setting Launcher.gmk change from: 8279007:
>> jstatd fails to start because SecurityManager is
> Remove the use of Security Manager from jstatd.
> Add use of an ObjectInputFilter to restrict RMI.
>
> Also we can undo the property-setting Launcher.gmk change from: 8279007:
> jstatd fails to start because SecurityManager is disabled
> ..as that is no longer needed.
>
> Docs/man page update
On Mon, 10 Jan 2022 11:17:12 GMT, Kevin Walls wrote:
>> Remove the use of Security Manager from jstatd.
>> Add use of an ObjectInputFilter to restrict RMI.
>>
>> Also we can undo the property-setting Launcher.gmk change from: 8279007:
>> jstatd fails to start because SecurityManager is
On Mon, 10 Jan 2022 11:17:12 GMT, Kevin Walls wrote:
>> Remove the use of Security Manager from jstatd.
>> Add use of an ObjectInputFilter to restrict RMI.
>>
>> Also we can undo the property-setting Launcher.gmk change from: 8279007:
>> jstatd fails to start because SecurityManager is
On Thu, 27 Jan 2022 11:32:18 GMT, Alex Menkov wrote:
>> Changes:
>> - ClassFileReconstituter is updated to restore "MethodParameters" attribute;
>> - handling of the attribute in VM_RedefineClasses is moved to be consistent
>> with other code (like local variable table);
>> - copied
On Thu, 27 Jan 2022 09:17:09 GMT, Yi Yang wrote:
>> Add VM.classes to print details of all classes, output looks like:
>>
>> 1. jcmd VM.classes
>>
>> KlassAddr Size State Flags LoaderName ClassName
>> 0x000800c0b400 62 inited W bootstrap
>>
On Thu, 27 Jan 2022 04:23:51 GMT, Chris Plummer wrote:
>> Alex Menkov has updated the pull request incrementally with one additional
>> commit since the last revision:
>>
>> Simplified the test, added comments
>
> src/hotspot/share/prims/jvmtiRedefineClasses.cpp line 3692:
>
>> 3690:
> Changes:
> - ClassFileReconstituter is updated to restore "MethodParameters" attribute;
> - handling of the attribute in VM_RedefineClasses is moved to be consistent
> with other code (like local variable table);
> - copied ClassTransformer class (from test/jdk/com/sun/jdi/lib/jdb) to
>
On Mon, 24 Jan 2022 04:12:22 GMT, Ioi Lam wrote:
>> Yi Yang has updated the pull request incrementally with one additional
>> commit since the last revision:
>>
>> fix test
>
> src/hotspot/share/oops/instanceKlass.cpp line 2106:
>
>> 2104: // classloader name
>> 2105: ClassLoaderData*
> Add VM.classes to print details of all classes, output looks like:
>
> 1. jcmd VM.classes
>
> KlassAddr Size State Flags LoaderName ClassName
> 0x000800c0b400 62 inited W bootstrap
> java.lang.invoke.LambdaForm$MH/0x000800c0b400
> 0x000800c0b000 62 inited W bootstrap
>
24 matches
Mail list logo
