Bug 468097 - NullPointerException in ReferenceBinding$3.compare (98)
Summary: NullPointerException in ReferenceBinding$3.compare (98)
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 4.5   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2015-05-23 00:06 EDT by EPP Error Reports CLA
Modified: 2023-04-27 16:48 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description EPP Error Reports CLA 2015-05-23 00:06:26 EDT
The following incident was reported via the automated error reporting:


    code:                   2
    plugin:                 org.eclipse.core.jobs_3.7.0.v20141128-1953
    message:                An internal error occurred during: "Java Search".
    fingerprint:            d03fc78a
    exception class:        java.lang.NullPointerException
    exception message:      -
    number of children:     0
    
    java.lang.NullPointerException: null
    at org.eclipse.jdt.internal.compiler.lookup.ReferenceBinding$3.compare(ReferenceBinding.java:98)
    at org.eclipse.jdt.internal.compiler.lookup.ReferenceBinding$3.compare(ReferenceBinding.java:1)
    at java.util.TimSort.countRunAndMakeAscending(null:-1)
    at java.util.TimSort.sort(null:-1)
    at java.util.Arrays.sort(null:-1)
    at org.eclipse.jdt.internal.compiler.lookup.ReferenceBinding.sortMethods(ReferenceBinding.java:221)
    at org.eclipse.jdt.internal.compiler.lookup.BinaryTypeBinding.availableMethods(BinaryTypeBinding.java:355)
    at org.eclipse.jdt.internal.core.search.matching.ClassFileMatchLocator.locateMatches(ClassFileMatchLocator.java:200)
    at org.eclipse.jdt.internal.core.search.matching.MatchLocator.process(MatchLocator.java:1816)
    at org.eclipse.jdt.internal.core.search.matching.MatchLocator.locateMatches(MatchLocator.java:1259)
    at org.eclipse.jdt.internal.core.search.matching.MatchLocator.locateMatches(MatchLocator.java:1300)
    at org.eclipse.jdt.internal.core.search.matching.MatchLocator.locateMatches(MatchLocator.java:1432)
    at org.eclipse.jdt.internal.core.search.JavaSearchParticipant.locateMatches(JavaSearchParticipant.java:122)
    at org.eclipse.jdt.internal.core.search.BasicSearchEngine.findMatches(BasicSearchEngine.java:232)
    at org.eclipse.jdt.internal.core.search.BasicSearchEngine.search(BasicSearchEngine.java:516)
    at org.eclipse.jdt.core.search.SearchEngine.search(SearchEngine.java:584)
    at org.eclipse.jdt.internal.ui.search.JavaSearchQuery.run(JavaSearchQuery.java:144)
    at org.eclipse.search2.internal.ui.InternalSearchUI$InternalSearchJob.run(InternalSearchUI.java:91)
    at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
   
  

General Information:

    reported-by:      
    anonymous-id:     016aaff7-9f81-38ad-8ec7-ab6ce1631d33
    eclipse-build-id: 4.5.0.I20141210-2000
    eclipse-product:  org.eclipse.epp.package.modeling.product
    operating system: Windows8 6.3.0 (x86_64) - win32
    jre-version:      1.8.0-b132

The following plug-ins were present on the execution stack (*):
    1. org.eclipse.core.jobs_3.7.0.v20141128-1953
    2. org.eclipse.jdt_3.11.0.v20141210-2000
    3. org.eclipse.jdt.core_3.11.0.v20141209-1931
    4. org.eclipse.jdt.ui_3.10.100.v20141208-1433

Please note that:
* Messages, stacktraces, and nested status objects may be shortened.
* Bug fields like status, resolution, and whiteboard are sent
  back to reporters.
* The list of present bundles and their respective versions was
  calculated by package naming heuristics. This may or may not reflect reality.

Other Resources:
* Report: https://dev.eclipse.org/recommenders/committers/confess/#/problems/54c4f47dbee810030da0b684  
* Manual: https://dev.eclipse.org/recommenders/community/confess/#/guide


Thank you for your assistance.
Your friendly error-reports-inbox.
Comment 1 Jay Arthanareeswaran CLA 2015-05-26 01:23:28 EDT
Hmm.. One of the possibilities is that resolveTypesFor(MethodBinding) returns null in BinaryTypeBinding#availableMethods(). But I am only guessing and we need a testcase to progress further on this.
Comment 2 Eclipse Genie CLA 2020-09-01 17:06:19 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 3 Eclipse Genie CLA 2023-04-27 16:48:25 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.