Bug 90027 - [WorkbenchParts] NPE when starting a search in M5a
Summary: [WorkbenchParts] NPE when starting a search in M5a
Status: ASSIGNED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.1   Edit
Hardware: PC Linux-GTK
: P5 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-04-01 15:24 EST by Oyvind Harboe CLA
Modified: 2019-09-06 16:15 EDT (History)
0 users

See Also:


Attachments
Shows NPE in debugger (234.79 KB, image/pjpeg)
2005-04-01 15:25 EST, Oyvind Harboe CLA
no flags Details
Lots of exceptions in log.... (115.36 KB, text/plain)
2005-04-01 15:28 EST, Oyvind Harboe CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Oyvind Harboe CLA 2005-04-01 15:24:11 EST
I'll attach a picture with an NPE I got when starting a search.


Øyvind
Comment 1 Oyvind Harboe CLA 2005-04-01 15:25:01 EST
Created attachment 19459 [details]
Shows NPE in debugger
Comment 2 Oyvind Harboe CLA 2005-04-01 15:28:58 EST
Created attachment 19460 [details]
Lots of exceptions in log....
Comment 3 Oyvind Harboe CLA 2005-04-01 15:43:20 EST
After restarting Eclipse, the problem went away. I've only seen this once.

Unless the exceptions can say something immediately valuable, feel free to 
close this PR as I don't think this is something that I'll be able to 
reproduce.

Øyvind
Comment 4 Dani Megert CLA 2005-04-01 15:47:30 EST
an NPE always tells a story ;-)
Comment 5 Oyvind Harboe CLA 2005-04-01 15:55:20 EST
>an NPE always tells a story ;-)

I wish the same was true for OutOfMemory exceptions. Sigh.... ;-)
Comment 6 Martin Aeschlimann CLA 2005-04-04 04:56:34 EDT
There are several NPE's in your stacktrace. The one in the screenshot is the
following one.
Moving to platform.ui


java.lang.NullPointerException
	at org.eclipse.ui.internal.WorkbenchPage.isPartVisible(WorkbenchPage.java:2058)
	at
org.eclipse.search2.internal.ui.text.WindowAnnotationManager.initEditors(WindowAnnotationManager.java:86)
	at
org.eclipse.search2.internal.ui.text.WindowAnnotationManager.<init>(WindowAnnotationManager.java:34)
	at
org.eclipse.search2.internal.ui.text.AnnotationManagers.searchResultActivated(AnnotationManagers.java:56)
	at
org.eclipse.search.ui.text.AbstractTextSearchViewPage.setInput(AbstractTextSearchViewPage.java:695)
	at org.eclipse.search2.internal.ui.SearchView.showSearchResult(SearchView.java:258)
	at org.eclipse.search2.internal.ui.SearchView.queryAdded(SearchView.java:343)
	at org.eclipse.search2.internal.ui.QueryManager.fireAdded(QueryManager.java:76)
	at org.eclipse.search2.internal.ui.QueryManager.addQuery(QueryManager.java:53)
	at
org.eclipse.search2.internal.ui.InternalSearchUI.addQuery(InternalSearchUI.java:303)
	at
org.eclipse.search2.internal.ui.InternalSearchUI.runSearchInBackground(InternalSearchUI.java:157)
	at org.eclipse.search.ui.NewSearchUI.runQueryInBackground(NewSearchUI.java:92)
	at
org.eclipse.search.internal.ui.text.TextSearchPage.performAction(TextSearchPage.java:185)
	at org.eclipse.search.internal.ui.SearchDialog.performAction(SearchDialog.java:373)
	at
org.eclipse.search.internal.ui.util.ExtendedDialogWindow.buttonPressed(ExtendedDialogWindow.java:161)
	at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:543)
	at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:89)
Comment 7 Paul Webster CLA 2006-09-28 14:07:20 EDT
Is this still a problem in 3.3?

PW
Comment 8 Denis Roy CLA 2007-06-22 09:32:51 EDT
Changes requested on bug 193523
Comment 9 Eclipse Webmaster CLA 2019-09-06 16:15:05 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.