-
Notifications
You must be signed in to change notification settings - Fork 729
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
JTReg Test Fail: sun/nio/cs/FindDecoderBugs.java #8992
Comments
Tagging as jit
fyi @fjeremic |
Launching a grinder to find reproducibility rate: |
Grinder is showing 1/10 failure rate. Unfortunately debug symbols are not present in the JVM which ran this build (#8874 is tracking the fix), so I had to work around to get the symbols. I downloaded the same nightly build [1] and loaded the core file from the failure job.
Running this script yields:
So the issue happens in the optimizer while creating usedef info. @PushkarBettadpur could you please help the optimizer team investigate this one? Let's help the experts collect trace logs with necessary tracing information so we can determine what went wrong. As a first step please reach out to @andrewcraik and/or @cathyzhyi to figure out what tracing options we may need, then let's help collect the logging. |
The dataflow engine has been very stable - I would suggest running traceFull paranoidOptCheck and see if we can make sure the trees are valid before the opt. |
Took a stab at this recently and unfortunately what I'm finding is that once I start adding any tracing options, the failure isn't reproducible anymore. Perhaps |
The following is a grinder from a nightly build a few days ago which shows the failure is still present: This problem is effectively impossible to reproduce with logging as the benchmark runs only for several seconds and is very sensitive to any tracing. Even with a specific inlining plan I was not able to get a reproduction of the issue massaging the command line. However #9120 to the rescue! Using my latest set of prototype changes to improvements to the jitdump I am able to gather the necessary logs with jitdump.20200427.140209.43974.0004.zip The crash happens here:
Which seems to correspond to the following source code location: The call ( Which gets inlined into the crashing function. We can see this because the first thing we do in the equality operator is compare the value of That is, (8 + 8 + 4 + 4). And this aligns with the instruction sequence which loads 24 bytes off from the object returned by @andrewcraik I think we'll need an expert in this area to take a look at the log. Transferring the issue over to you. I can collect additional tracing if needed via the jitdump mechanism. @vijaysun-omr FYI for jitdump work paying dividends already. |
Paraphrasing from the following comment #8758 (comment), to get the legacy verifier to report errors, you have to be running a debug build of the JIT, define the |
Failure link
JDK8/J9
Optional info
Failure output (captured from console output)
Dump Files https://ibm.box.com/shared/static/bq89d6wwq34eg7j85gji425fc4r1ixxd.gz
The text was updated successfully, but these errors were encountered: