View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0004160||Rocky-Linux-9||java-1.8.0-openjdk||public||2023-09-07 17:44||2023-09-09 03:30|
|Reporter||Areth Kellejian||Assigned To||Neil Hanlon|
|Status||closed||Resolution||unable to reproduce|
|Summary||0004160: Latest OpenJDK leaking memory on latest Rocky 9. No leak on Centos 7|
|Description||We noticed a huge memory leak in our application. We were able to figure out the problem is with JIT. When we disabled JIT on Rocky 9.2, the problem stopped. The difference between Centos 7 and Rocky 9 is the version of glibc, v2.17 vs v2.34. This memory leak was observed when we went from Centos 7 to Rocky 9. We had to revert back to Centos 7. If you need more details, let me know.|
|Tags||No tags attached.|
Thank you for bringing this issue to our attention. Memory leaks in the JVM can be complex, and it's essential to gather relevant information for debugging.
To investigate further and potentially resolve this issue, we recommend the following steps:
Debugging the JVM:
Please refer to the official OpenJDK documentation for debugging memory issues. It provides guidance on tools and techniques for analyzing JVM memory usage and identifying memory leaks.
You can start by using tools like jmap, jstack, and jconsole to collect JVM heap dumps, thread dumps, and monitor memory usage.
If you suspect the issue is related to JIT compilation, consider disabling JIT temporarily for debugging purposes using the -Xint flag. This will interpret the bytecode instead of compiling it, which can help isolate the problem.
Reviewing JVM Parameters:
Ensure that you are using appropriate JVM parameters and options for your application. Incorrect JVM settings can lead to memory issues.
Collect Logs and Information:
Capture any relevant logs, error messages, or stack traces related to the memory leak. This information will be valuable in pinpointing the issue.
Review any third-party libraries or dependencies used by your application that might interact with the JVM or glibc. Ensure they are compatible with your environment.
Consider reporting this problem to the upstream CentOS Stream and/or OpenJDK project communities. They may have insights or fixes related to glibc version differences--though I highly suspect that this glibc difference is a red herring. Java JIT and glibc have little to do with one another in this context.
We understand that debugging such issues can be challenging, and we encourage you to leverage the broader community and resources available to diagnose and potentially resolve this problem.
If you have any specific findings or require further assistance, please feel free to share them with us, but please remember that Rocky, as a downstream distribution of Red Hat Enterprise Linux, will functional exactly the same as RHEL, and such bugs must be reported upstream for them to be addressed in Rocky core.
|2023-09-07 17:44||Areth Kellejian||New Issue|
|2023-09-09 03:30||Neil Hanlon||Assigned To||=> Neil Hanlon|
|2023-09-09 03:30||Neil Hanlon||Status||new => closed|
|2023-09-09 03:30||Neil Hanlon||Resolution||open => unable to reproduce|
|2023-09-09 03:30||Neil Hanlon||Note Added: 0004595|