JDK-8062253 : NullPointerException in com.sun.tools.javac.code.Types.isConvertible
  • Type: Bug
  • Component: tools
  • Sub-Component: javac
  • Affected Version: 8u25
  • Priority: P4
  • Status: Closed
  • Resolution: Cannot Reproduce
  • OS: linux
  • CPU: x86_64
  • Submitted: 2014-10-22
  • Updated: 2015-02-09
  • Resolved: 2015-02-09
Related Reports
Duplicate :  
Duplicate :  
Relates :  
Description
FULL PRODUCT VERSION :
java version "1.8.0_25"
Java(TM) SE Runtime Environment (build 1.8.0_25-b17)
Java HotSpot(TM) 64-Bit Server VM (build 25.25-b02, mixed mode)


ADDITIONAL OS VERSION INFORMATION :
Linux 3.13.0-37-generic #64-Ubuntu SMP Mon Sep 22 21:28:38 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux


A DESCRIPTION OF THE PROBLEM :
The bug https://bugs.openjdk.java.net/browse/JDK-8056038 still persists.
Of course it would be much easier to just comment on the bug in the issue tracker, but I don't see how to do so.  How do I get an account or how do I add comments anonymously?

So instead of adding just a comment "affects also Java 8u25" I have to create a completely new bug report via this website for every affected Java release.  Thank you very much!

Actually I'm not sure anymore what is worse: Is it this critical bug which causes major security issues in my company since all employees are forced to stay with an outdated Java or is it the whole process of reporting Java bugs.  I really haven't seen such a closed bug tracking system for years now.  How can this be related to an "openjdk"???  One really gets the feeling you are not interested in bug reports at all!  Otherwise you would not try to make reports as hard and intransparent as possible (I did not even get a notification for my last bug report, neither that it was created nor that it was closed as duplicate.  I had to search for it on the web myself).  So please don't wonder if people switch to Scala or other languages.  They ALL have a better understanding of how to work with the community.  Or look at JetBrains and how they handle users of their open source or commercial products:  Of course they allow users to report bugs in their issue tracker and they also inform the users about changes.  That's how one does it!

ADDITIONAL REGRESSION INFORMATION: 
Same as on https://bugs.openjdk.java.net/browse/JDK-8056038.

STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
Same as on https://bugs.openjdk.java.net/browse/JDK-8056038.

EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
Same as on https://bugs.openjdk.java.net/browse/JDK-8056038.
ACTUAL -
Same as on https://bugs.openjdk.java.net/browse/JDK-8056038.

ERROR MESSAGES/STACK TRACES THAT OCCUR :
Same as on https://bugs.openjdk.java.net/browse/JDK-8056038.

REPRODUCIBILITY :
This bug can be reproduced always.

---------- BEGIN SOURCE ----------
Same as on https://bugs.openjdk.java.net/browse/JDK-8056038.
---------- END SOURCE ----------

CUSTOMER SUBMITTED WORKAROUND :
Same as on https://bugs.openjdk.java.net/browse/JDK-8056038.


Comments
This has been opened for long - and that is misleading, given that the underlying issue has been fixed. I'm closing it, with a view of reopening if the submitter comes back and says it's not fixed.
09-02-2015

The fix for JDK-8044546 which is the one that fixes this issue too has been targeted to 8u40 so is normal that the user can't see it in 8u25. I have sent a mail to the user. The problem is fixed in repo [1] but I will wait for his confirmation to close this bug as a duplicate. [1] http://hg.openjdk.java.net/jdk8u/jdk8u-dev/langtools
28-10-2014

User confirms that the resolution provided in 8u20 (JDK-8046357) fails for 8u25.
28-10-2014