#Java 11 crash with SIGSEGV when using Shenandoah Garbage Collector
1 messages · Page 1 of 1 (latest)
Can you try to use latest?
wow
yeah, ^latest
go to 21
(and the program I am running only supports java 11).
👀
fuckin
why
lets solve that problem first
Updating the major java version is just not possible
I will help you do this for free.
i'm not joking
i want to know where the issues are so i can fix them in open source however i can
can't you use the default gc ?
And note that Shenandoah was only production ready since java 15 https://openjdk.org/jeps/379, so I would say that it is normal that such bug can happen before java 15
you could also maybe try to update the patch version since a backport may have been done
But
do you not have a test server where you can test such thing ? so you can check if updating to latest patch of java 8/11 or update to java 15+ solve the issue ?
what about ZGC ?
ZGC is only java 17+, I think?
Shenandoah in experimental since 12 https://openjdk.org/jeps/189 and production since 15 https://openjdk.org/jeps/379
ZGC is in experimental since 11 https://openjdk.org/jeps/333 and production since 15 https://openjdk.org/jeps/377
so if you can use any of those two in pre java 12
then it must be a backport or something like that
well yea, backport
I don't know about ZGC, but yes you're correct - Shenandoah was backported to 11
are they differences between the two servers in term of OS or architecture ?
unsafe usage, internal poking at apis, or c extensions?
What you can do are
- Ignore the issue and update java/change GC
- Try to find the cause or try to fix it
-- by reproducing it
-- by updating either patch or major
-- by filing a bug report (but I doubt it would help if you are not using the latest patch, because then they would ask if it works on latest patch, you could try tho)
you could try to see the load on the gc, you could enable debug info about the gc, you could check that no there is no unsafe/native stuff that could break it