JDK-8155797 : Create regression test for issue fixed by JDK-8148786
  • Type: Bug
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: 9
  • Priority: P2
  • Status: Closed
  • Resolution: Won't Fix
  • Submitted: 2016-05-02
  • Updated: 2019-09-13
  • Resolved: 2017-02-20
Related Reports
Relates :  
There is no test specifically testing fix for JDK-8148786.
A duplicate (JDK-8149727) contains quite ready-to-use code:

// The following code fails with "IS NULL2": 
for (int i = 0; i < types.length; i++) {
  if (types[i].getInternalType() == null) {
    throw new AssertionError("IS NULL1");
  itypes[i] = types[i].getInternalType();
for (int i = 0; i < itypes.length; ++i) {
  if (itypes[i] == null) {
    throw new AssertionError("IS NULL2");
JDK-8148786 is very hard to reproduce and it's not possible to write a simple regression test to trigger this problem. The "quite ready-to-use" code mentioned above only triggers the problem in a very specific environment (inlining, profiling information, optimizations) and does not work as standalone regression test. I'm closing this as "Won't fix".

Yes. there is a problem. I wasn't able to successfully reproduce this problem on affected b105. Even 1000 launches wasn't enough. And also, I wasn't able to reproduce problem by running originally mentioned applications of this build. So, this problem is kind of "hard-to-reproduce" currently

are there any problems w/ integration of mentioned code as a regression test?

ILW = missing coverage leading to false confidence in quality; always; none = MHH = P2