Bug 536014 - NPE when hovering the launch toolbar icon
Summary: NPE when hovering the launch toolbar icon
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 4.7.3   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2018-06-18 10:55 EDT by Robert Kiss CLA
Modified: 2022-07-09 19:01 EDT (History)
2 users (show)

See Also:


Attachments
Eclipse project to reproduce (6.55 KB, application/zip)
2018-06-18 10:55 EDT, Robert Kiss CLA
no flags Details
Eclipse log file (11.40 KB, text/x-log)
2018-06-18 10:56 EDT, Robert Kiss CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Robert Kiss CLA 2018-06-18 10:55:47 EDT
Created attachment 274508 [details]
Eclipse project to reproduce

Eclipse IDE for Eclipse Committers
Version: Oxygen.3a Release (4.7.3a)
Build id: 20180405-1200

Steps to reproduce:
- Import attached project
- Open BugReproTest class
- Hover Lunch toolbar action -> An error dialog will be displayed.

Also, when hovering the "Run as" or "Debug as" context menu entries of the above mentioned class logs a NPE. See attached log for details.
Comment 1 Robert Kiss CLA 2018-06-18 10:56:23 EDT
Created attachment 274509 [details]
Eclipse log file
Comment 2 Jay Arthanareeswaran CLA 2018-06-18 11:40:55 EDT
Reproduced with master. As per the log and the reported version 4.7.3a, the line on top of the stack is this:

public Constant optimizedBooleanConstant() {
	switch (this.resolvedType.id) { // where the NPE occurs


And the code in question is this:

pp.rs = ! (boolean) pp.rs;

And the presence of "!' seem to cause the resolvedType to be null somehow.
Comment 3 Stephan Herrmann CLA 2018-06-18 12:24:29 EDT
This looks just like bug 489979, perhaps even based on the same code? :)
Comment 4 Jay Arthanareeswaran CLA 2018-06-19 10:52:15 EDT
(In reply to Stephan Herrmann from comment #3)
> This looks just like bug 489979, perhaps even based on the same code? :)

Indeed. I had spent some time (luckily not so much) to arrive at the same conclusion that Sasi did (bug 489979, comment #4).

And your suggestion looks like a better option in terms of performance. Will see what it takes.
Comment 5 Eclipse Genie CLA 2020-07-07 02:15:31 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 6 Eclipse Genie CLA 2022-07-09 19:01:29 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.