-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Linux Core Dump with OOM #5470
Comments
You can see a bunch of OutOfMemoryErrors in the hs-err log just before the crash:
The very last one happens when a Truffle compiler is trying to translate a BTW, is there any console output at the time of failure? I would expect some kind of exception stack trace. |
I do see one possible cause for the Linux Core Dump which is where a ResourceArea buffer is allocated to transfer an encoded exception between the 2 heaps: https://github.com/graalvm/labs-openjdk-17/blob/f6b18b596fa5acb1ab7efa10e284d106669040a6/src/hotspot/share/jvmci/jvmciEnv.cpp#L318 |
Here is the only Console Output I have. I do have the core.XXXX file, let me know if you want that file. |
One interesting part of the output is the OOM during deopt.
this could cause some strange executions as the OOM occurs at a place which normally might not be expected to have an OOM. I don't know whether that's a factor or not. |
I've opened https://bugs.openjdk.org/browse/JDK-8297431 to increase the robustness of this code path in the JDK. |
This should now have been fixed by https://bugs.openjdk.org/browse/JDK-8297431. |
Describe the issue
We are getting an OOM in one of our environments. Along with this OOM, we are getting a Linux Core Dump. After doing the following test, we think there is a situation when the MetaSpace is full and an OOM is thrown GraalVM will, also, throw a Linux Core Dump.
-Xmx1024m -XX:MaxMetaspaceSize=256m
. This is where the Linux Core Dump and OOM was thrown.-Xmx2048m -XX:MaxMetaspaceSize=256m
and did not get either. Process took a little longer, but did finish.-Xmx1024m
, and removed the-XX:MaxMetaspaceSize
to allow it to be set to default (unlimited). We got the OOM, but not the Linux Core Dump-Xmx2048m
, and leaving-XX:MaxMetaspaceSize
set to default (unlimited). Waiting for this test to finish, but (based on 2 above) my suspicion is that neither the OOM, nor the Linux Core Dump will be thrown. There should be plenty of space for the process to finish. Will update this issue if we get some other error.What we are suspecting is that when the MetaSpace is full (and limited) and an OOM is thrown; a Linux Core Dump is thrown. Not sure if this is just a Centos 7 problem, or seen on other linux distros.
Expected behavior is an OOM would just be thrown, but no Linux Core Dump would happen.
Steps to reproduce the issue
Throw an Out of Memory in the JVM Heap and have the JVM Meta Data Space full at the same time.
Describe GraalVM and your environment:
We are running on an AWS EC2 instance that has the centos 7 image.
More details
hs_err_pid22374.log
The text was updated successfully, but these errors were encountered: