Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

JVM Crash when loading CRT #600

Closed
jpg0 opened this issue Oct 19, 2024 · 3 comments
Closed

JVM Crash when loading CRT #600

jpg0 opened this issue Oct 19, 2024 · 3 comments
Labels
bug This issue is a bug. p2 This is a standard priority issue response-requested Waiting on additional info and feedback. Will move to "closing-soon" in 2 days.

Comments

@jpg0
Copy link

jpg0 commented Oct 19, 2024

Describe the bug

When my java code attempts to load anything that depends on CRT, the JVM crashes when it's loaded.

Expected Behavior

No crash

Current Behavior

JVM crashes and (sometimes) produces a core dump and error log.

Reproduction Steps

Currently this only happens in quite a large application, teasing it apart into a single case isn't simple. The same code appears ok when run standalone.

Possible Solution

No response

Additional Information/Context

There is loads of data in the error log:

hs_err_pid25.log

SDK version used

1.21.0

Environment details (OS name and version, etc.)

Ubuntu 22.04 docker host, Debian guest; aarch64

@jpg0 jpg0 added bug This issue is a bug. needs-triage This issue or PR still needs to be triaged. labels Oct 19, 2024
@jmklix
Copy link
Member

jmklix commented Oct 31, 2024

Can you provide more details about this crash and your environment:

  • What java version are you using?
  • are you installing this sdk from source or mvn?
  • is everything set up correctly to run on arm?
  • a docker container that reproduces your environment
  • any other details that might be helpful for debugging.

@jmklix jmklix added response-requested Waiting on additional info and feedback. Will move to "closing-soon" in 2 days. p2 This is a standard priority issue and removed needs-triage This issue or PR still needs to be triaged. labels Oct 31, 2024
@jpg0
Copy link
Author

jpg0 commented Nov 1, 2024

I ended up building the CRT myself with debug symbols, and it would crash due to a missing GLIBC 2.32 dependency. I realised that I was using Debian 11 which ships GLIBC 2.31, so switched to Debian 12. This has ultimately fixed the problem for me, however it did require quite a lot of work on my behalf to figure out the problem. It would be good if there were some message in the logs etc that explained the problem, rather than just a hard crash. Regardless, I'll close this issue now.

@jpg0 jpg0 closed this as completed Nov 1, 2024
Copy link

github-actions bot commented Nov 1, 2024

This issue is now closed. Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug This issue is a bug. p2 This is a standard priority issue response-requested Waiting on additional info and feedback. Will move to "closing-soon" in 2 days.
Projects
None yet
Development

No branches or pull requests

2 participants