-
-
Notifications
You must be signed in to change notification settings - Fork 925
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 segfault with 9K and -noverify #2566
Comments
Ok, this probably means there's some bad bytecode being jitted. Could you do a run with the following flags (and noverify OFF) so we might see the problem with the bytecode?
|
BTW, JRuby's normal command line does boot JRuby itself into the boot classloader, skipping verification. Turning on noverify would only help libraries your app loads or other JVM bytecode loaded after JRuby has started up. Also look into the --dev flag for better startup times. |
I put the above failing code into
This was using 0902cd3
A similar error was generated using a4e929d, and JDK 1.7, which was the version used when this was initially reported. |
Marking as duplicate of #2910 |
I tried running the test-suite of one of our larger code-bases against jruby-head, and to my surprise the JVM suddenly segfaulted halfway through.
After some digging, I realized that the crash only happened when running with the option
-J-noverify
. At some point I put this flag intoJRUBY_OPTS
in order to improve start-up time. If I remove this flag, I see no crash, and no sign of any problem whatsoever. Similarly, if I run in jruby-1.7 (with or without-J-noverify
) everything works well. Is this flag no longer supported by jruby-head?I'm guessing some part of the new bytecode generation is the cause for the particular issue, and to that end I spent some time reducing thousands of lines of code to the following short snippet. With this snippet I can consistently reproduce the issue:
Beyond this point, I wasn't able to remove any more parts while retaining the segfault. I'm guessing that the next step to understand what is going on here, but I wouldn't really know where to start.
The text was updated successfully, but these errors were encountered: