Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 167277 - Info: "Failed to refresh Task List " in org.eclipse.mylar.core
Summary: Info: "Failed to refresh Task List " in org.eclipse.mylar.core
Status: RESOLVED DUPLICATE of bug 132450
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Mylyn (show other bugs)
Version: 0.9   Edit
Hardware: PC Windows XP
: P3 minor (vote)
Target Milestone: ---   Edit
Assignee: Mik Kersten CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-12-08 14:30 EST by maarten meijer CLA
Modified: 2006-12-08 15:28 EST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description maarten meijer CLA 2006-12-08 14:30:34 EST
-- Error Log --
Date: Fri Dec 08 20:27:14 CET 2006
Message: Failed to refresh Task List

Severity:
Info
Plugin ID: org.eclipse.mylar.core
Stack Trace:
org.eclipse.swt.SWTException: Widget
is disposed
	at org.eclipse.swt.SWT.error(SWT.java:3374)
	at org.eclipse.swt.SWT.error(SWT.java:3297)
	at
org.eclipse.swt.SWT.error(SWT.java:3268)
	at org.eclipse.swt.widgets.Widget.error(Widget.java:435)
	at
org.eclipse.swt.widgets.Widget.checkWidget(Widget.java:330)
	at org.eclipse.swt.widgets.TreeItem.getItemCount(TreeItem.java:732)
	at
org.eclipse.jface.viewers.TreeViewer.getItemCount(TreeViewer.java:437)
	at org.eclipse.jface.viewers.AbstractTreeViewer.updatePlus(AbstractTreeViewer.java:2486)
	at
org.eclipse.jface.viewers.AbstractTreeViewer.internalRefresh(AbstractTreeViewer.java:1617)
	at
org.eclipse.jface.viewers.AbstractTreeViewer.internalRefresh(AbstractTreeViewer.java:1582)
	at
org.eclipse.jface.viewers.StructuredViewer$8.run(StructuredViewer.java:1415)
	at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1323)
	at
org.eclipse.jface.viewers.StructuredViewer.refresh(StructuredViewer.java:1413)
	at org.eclipse.mylar.internal.tasks.ui.views.TaskListView.refresh(TaskListView.java:1443)
	at
org.eclipse.mylar.internal.tasks.ui.views.TaskListView.access$2(TaskListView.java:1395)
	at
org.eclipse.mylar.internal.tasks.ui.views.TaskListView$2$8.run(TaskListView.java:382)
	at
org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
	at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:123)
	at
org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3325)
	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2971)
	at
org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1914)
	at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1878)
	at
org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:419)
	at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
	at
org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:95)
	at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:78)
	at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:92)
	at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:68)
	at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:177)
	at
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown
Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
	at java.lang.reflect.Method.invoke(Unknown
Source)
	at org.eclipse.core.launcher.Main.invokeFramework(Main.java:336)
	at org.eclipse.core.launcher.Main.basicRun(Main.java:280)
	at
org.eclipse.core.launcher.Main.run(Main.java:977)
	at org.eclipse.core.launcher.Main.main(Main.java:952)
Comment 1 Robert Elves CLA 2006-12-08 14:39:21 EST
Did this happen at workbench startup or shutdown? Did it result in any adverse behaviour? Can you reproduce this and if so what steps?
Comment 2 Eugene Kuleshov CLA 2006-12-08 14:40:45 EST
I wonder if we should add version of Mylar to this automatic report submission if stack trace has Mylar packages...
Comment 3 Mik Kersten CLA 2006-12-08 14:53:15 EST
All the bugs that I have seen of this sort have been minor because they cause no bad behavior, and they may be with platform's refresh of the tree.  Let us know the answers to comment#1 in case we should investigate anything before 1.0.
Comment 4 maarten meijer CLA 2006-12-08 15:04:41 EST
It happened at workbench startup after updating (two steps required unfortunately)  to 0.9.2
A dialog was displayed prompting me to look at the log. There I saw it was mylar and used the 'Report as Bug' action.
I checked for duplicates (non found) so I submitted. It did not occur again after subsequent launches of Eclipse.

I feel that when an error produces a dialog it should be reported, if it's minor just log it and have a generic 'Submit log file for analysis action' to help developers of all Eclipse tools. This could the analyse and distribute to all teams... (only dreaming). I follow thsi closely and report back when it occurs again.
Comment 5 Mik Kersten CLA 2006-12-08 15:28:21 EST
Looks like this happened because you had a partially-updated Mylar, which is the very annoying update manager bug 132450.  We document the work around (don't use "Search for updates...") on the download page: http://www.eclipse.org/mylar/dl.php

Yes, this kind of error should definitely be reported as you did.  It usually helps to have more info with the automated reporting, so we should figure out a way to encourage that in our UI.

*** This bug has been marked as a duplicate of bug 132450 ***