Compile error in multi type catch block with Java 11, runtime error with Java 17

2023-03-29 Thread S A
Hi all, could someone clarify the following difference in javac behavior between Java 11 and Java 17? Which one is correct? There are two source files: package p; public class Exceptions { private static class E extends Exception { public void m() { } } public static class E1

Fwd: jdwp documentation for Java 9+

2022-06-16 Thread S A
Hi all, where can I find jwdp documentation (including list of arguments) for Java 9+? Background: A colleague of mine ran into this issue: https://bugs.openjdk.org/browse/JDK-8175050 I've since read that with Java 9+ also the hostname should be specified, to ensure remote debugging is possible

Re: Fwd: jdwp documentation for Java 9+

2022-06-16 Thread S A
Alright, thanks for the infos! On Thu, 16 Jun 2022 at 18:37, Chris Plummer wrote: > > On 6/16/22 3:07 AM, S A wrote: > > Hi all, > > > > where can I find jwdp documentation (including list of arguments) for > > Java 9+? > > > > Background: >

JIT compiler turned off after stepping over in jdb

2022-10-31 Thread S A
Hi all, TL;DR We observe a significant performance degradation after stepping over in a debugger. By the looks of it, the interpreter only mode is entered and never left due to this change: https://github.com/openjdk/jdk11u/commit/dbb9eb5b9c3ddcbcfaae8ac4ca21760c9c99a15c#diff-fa220f091e99b08a3a20

Class loader leaked when ForkJoinPool is used in loaded class, with Java 19+

2024-03-04 Thread S A
Hi all, after moving our application to Java 21 (up from Java 17), we noticed a class loader leak. A memory snapshot points to a ProtectionDomain object held by a ForkJoinWorkerThread, the protection domain holds the class loader and prevents GC. To reproduce outside of our application, we use th

Re: Stepping in debugger switches to interpretation mode

2024-05-31 Thread S A
On Fri, 2024-05-31 at 14:44 +0200, Maksim Zuev wrote: > Dear Sir/Madam, > > I encountered a problem while debugging the code. I am attaching the > reproducer to this email in the Main.java file. > > When running it with the debugger without stepping, the application > runs in less than a second (se