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 seg faulting sometimes with a Sinatra GET request using JRuby #521

Closed
nclaburn opened this issue Feb 2, 2013 · 6 comments
Closed

JVM seg faulting sometimes with a Sinatra GET request using JRuby #521

nclaburn opened this issue Feb 2, 2013 · 6 comments

Comments

@nclaburn
Copy link

nclaburn commented Feb 2, 2013

It's not repeatable on demand, but sometimes when my Sinatra app processes a GET request the JVM crashes. Below a link to the gists containing the hs_error logs.

gist for errors

@enebo
Copy link
Member

enebo commented Feb 28, 2013

If using -Xnative.enabled=false on JRuby's command line does not fix this then I strongly suspect this is a JVM bug in Java 7. Disabling native supports means all the posix APIs are implemented in pure Java which might not provide all the posix support your app needs. Nonetheless if you app starts without it then this should be helpful in eliminating a possible cause.

@chrisseaton
Copy link
Contributor

Are you still having this problem @nclaburn? Did you try -Xnative.enabled=false?

As @enebo says it is possible that it is a JVM bug (I've seen hard crashes in the JVM from normal JRuby code myself before).

@nclaburn
Copy link
Author

nclaburn commented Oct 8, 2014

@chrisseaton I haven't tried recently. I will do my best to repeat the process and will update this issue if/when I get time.

@headius
Copy link
Member

headius commented Nov 13, 2014

This is definitely a crash in the JVM...specifically in C1, the "client" compiler.

If you can reproduce this, we can have the JVM dump compiler logs that might give us some indication what's causing the crash..

@nclaburn
Copy link
Author

After many attempts I can no long reproduce this. My environment (including hardware) has evolved too much since discovering this. It is no longer an issue for me personally.

@rtyler
Copy link

rtyler commented Aug 7, 2015

Going to go ahead and close this since I do not believe there is anything for JRuby to do here :(

@rtyler rtyler closed this as completed Aug 7, 2015
@enebo enebo added this to the Invalid or Duplicate milestone Aug 20, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants