crash with ObjAllocator::initialize(HeapWordImpl**) const+0x1f

[finalch]

Expected Behavior

The related issue: #3409
This time, we have upgraded Netty's version (by upgrading springboot), we have over 100 instances and a crash occurred occasionally. probability was too low and no regularity, so difficult for us to locate and reproduce the problem.
please provide us with some help and suggestions, thakns.

Actual Behavior

one hs_err_pid.log
hs_err_pid51296.log

Possible Solution

honestly, I do not know

Your Environment

• Reactor version(s) used: 1.1.22(via spring-boot-starter-reactor-netty:3.3.4)
• Other relevant libraries versions (eg. netty, ...): spring-boot-starter-webflux:3.3.4
• JVM version (java -version):
  java version "17.0.1" 2021-10-19 LTS
  Java(TM) SE Runtime Environment (build 17.0.1+12-LTS-39)
  Java HotSpot(TM) 64-Bit Server VM (build 17.0.1+12-LTS-39, mixed mode, sharing)
• OS and version (eg. uname -a):

Linux xxxxxxxxxxxxxx 4.14.0_1-0-0-43 #1 SMP Wed Aug 18 10:05:21 CST 2021 x86_64 x86_64 x86_64 GNU/Linux

[violetagg]

@finalch Do you use netty tcnative and/or boringssl? If yes can you specify the version?

[finalch]

@finalch Do you use netty tcnative and/or boringssl? If yes can you specify the version?

@violetagg thanks for reply.
All netty-.jar and reactor-.jar in the my application jar are listed:

The tcnative is configurated in pom with test scope。

[violetagg]

@finalch The issue is during the production usage and not during testing, isn't it?

[finalch]

@violetagg yes