vertx-sql-client core dump with wisp2

[yueliangwen]

Description vertx-sql-client based on netty.

Steps to Reproduce Steps to reproduce the behavior:

1. Download the dump.tar.gz
2. Read the README.adoc
3. Configure the PostgreSQL instance
4. See core dump

dump.tar.gz hs_err_pid4247.log replay_pid4247.log

You may modify some configuration code to connect the PostgreSQL instance.

The README.adoc image

Expected behavior The case should not be core dump.

JDK version openjdk version "1.8.0_282" OpenJDK Runtime Environment (Alibaba Dragonwell 8.6.5) (build 1.8.0_282-b1) OpenJDK 64-Bit Server VM (Alibaba Dragonwell 8.6.5) (build 25.282-b1, mixed mode)

Execution environment

• OS and version: Linux ubuntu 5.8.0-45-generic #51~20.04.1-Ubuntu SMP Tue Feb 23 13:46:31 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

[zhengxiaolinX]

Thanks for opening this issue. You can simply add one JVM option -XX:CompileCommand=exclude,io.vertx.sqlclient.impl.SocketConnectionBase::lambda\$init\$0 to exclude this method from compilation or -XX:-TieredCompilation to disable the C1 compiler to work around with this issue in your case if needed. This problem happens because some dead locals in debug info of MonitorExit node in synchronized methods, compiled by the C1 compiler, don't get cleaned, and it is a somewhat rare case. I will file a patch afterward to fix this problem.

[yueliangwen]

@zhengxiaolinX Thanks for your suggestion.

[zhengxiaolinX]

Could you please have a try for the latest build, in which the fix for Wisp exists, when you are available? I hope everything goes well this time. Release page: Dragonwell8.6.6 Thanks in advance.

[yueliangwen]

@zhengxiaolinX Thanks, it worked as expected.

[zhengxiaolinX]

Thanks again for providing us with this great test for reproducing this issue, which helps us solve it without any difficulty. I'll close this issue and please feel free to reopen it if needed.