Bug 21717 - Null Pointer Exception in EditorWorkbook.java
Summary: Null Pointer Exception in EditorWorkbook.java
Status: RESOLVED FIXED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 2.0   Edit
Hardware: PC Windows 2000
: P1 critical (vote)
Target Milestone: 2.0.1   Edit
Assignee: Eduardo Pereira CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-07-18 19:20 EDT by David Sanders CLA
Modified: 2002-07-26 12:45 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description David Sanders CLA 2002-07-18 19:20:46 EDT 
Upon closing a project, I got an error such as
'Unable to restore editor <name>'.  Then I noticed
that I was able to double click on the blank background
where editors would normally be (no editor was open), and 
the blank 'gray' background would be 'maximized' as if an 
editor were there.  I then noticed this error message
in the log file:

!ENTRY org.eclipse.ui 4 0 Jul 18, 2002 16:29:07.800
!MESSAGE java.lang.NullPointerException
!STACK 0
java.lang.NullPointerException
	at org.eclipse.ui.internal.EditorWorkbook$4.mouseDown
(EditorWorkbook.java:165)
	at org.eclipse.swt.widgets.TypedListener.handleEvent
(TypedListener.java:126)
	at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:77)
	at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:827)
	at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:1529)
	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1291)
	at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1177)
	at org.eclipse.ui.internal.Workbench.run(Workbench.java:1160)
	at org.eclipse.core.internal.boot.InternalBootLoader.run
(InternalBootLoader.java:775)
	at org.eclipse.core.boot.BootLoader.run(BootLoader.java:432)
	at EclipseRuntimeLauncher.main(EclipseRuntimeLauncher.java:24)
Comment 1 David Sanders CLA 2002-07-22 13:40:56 EDT 
I am not sure if this is the case, but that particular editor may have been 
opened programmatically in a prior debug session (in a previous run of eclipse) 
by a source locator (using FileEditorInput).  I cannot tell you if this was the 
case, but it may offer some clues.
Comment 2 Eduardo Pereira CLA 2002-07-25 10:43:23 EDT 
Fix is released in HEAD and 201 streams.
Comment 3 Eduardo Pereira CLA 2002-07-26 12:45:51 EDT 
Fix released in both streams (201 and HEAD)