Open nirvdrum opened 4 days ago
Filed internally as GR-58225.
@nirvdrum After a quick look it would be really helpful or even necessary to get the hs_err
, could you try to get it?
@dougxc told me -XX:LogFile
(--vm.XX:LogFile=path
as a truffleruby arg) can be used to put the hs_err log anywhere.
I'm trying to get the hs_err log, but I'm still running into the limitation I mentioned in the issue description. Unfortunately, it doesn't really matter where I write the file as I don't have the means to mount a volume so the file goes away when the container is discarded. We have a crash reporting service based on core_pattern
that scans for hs_err and uploads them to a bucket, but it hasn't picked up these files. I'm trying to debug that, but it's a very slow process. I haven't yet been able to reproduce locally.
I'm not sure if it works, but maybe you could try -XX:LogFile=/dev/stdout
.
Describe GraalVM and your environment :
java -Xinternalversion
:Have you verified this issue still happens when using the latest snapshot? Yes. I only see the issue with snapshots since Puma support isn't yet available in a release.
Describe the issue
While running a Rails application with an GFTC EA snapshot of TruffleRuby with the Panama backend enabled I sometimes see the JVM crash. Unfortunately, since this happens during application boot, I don't have the hs_err log. I'm trying to work with our infrastructure team to preserve this. Currently, when it crashes the deployment is halted and the container used is immediately discarded. I do, however, have a copy of the core dump, but that is too large to attach to the issue.
Code snippet or code repository that reproduces the issue
Steps to reproduce the issue Please include both build steps as well as run steps
rbenv install truffleruby+graalvm-dev
export TRUFFLERUBYOPT="--experimental-options --ruby.cexts-panama"
Unfortunately, the crash doesn't occur reliably. Sometimes I get an exception instead, which I think is related to a known issue with the propagation of
errno
Expected behavior I'd expect the application to behave functionally the same both with and without Panama enabled.