Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 357622 - Asynchronous runnable seems to try to set an input to a disposed viewer
Summary: Asynchronous runnable seems to try to set an input to a disposed viewer
Status: RESOLVED INVALID
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: EMF-Facet (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P5 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-09-14 08:13 EDT by Remy Suen CLA
Modified: 2020-05-01 11:27 EDT (History)
3 users (show)

See Also:
gdupe: indigo+
gdupe: juno+
gdupe: kepler+

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 Remy Suen CLA 2011-09-14 08:13:57 EDT 
I had a view up (don't really remember which one) and closed it right after startup. Moments later I got an error dialog for this problem.

Caused by: java.lang.IllegalStateException: Need an underlying widget to be able to set the input.(Has the widget been disposed?)
	at org.eclipse.jface.viewers.StructuredViewer.setInput(StructuredViewer.java:1681)
	at org.eclipse.emf.facet.common.ui.internal.views.AbstractTreeView$3.run(AbstractTreeView.java:137)
	at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
	at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
	... 23 more
Comment 1 Gregoire Dupe CLA 2011-09-29 13:54:45 EDT 
Hello,

Which view causes this problem ?

Regards,
Grégoire
Comment 2 Remy Suen CLA 2011-09-29 13:59:44 EDT 
(In reply to comment #1)
> Which view causes this problem ?

Sorry, I don't remember.

Asynchronous messages can always be run after a widget has been disposed so I suggest some checks get added.
Comment 3 Lars Vogel CLA 2019-12-11 04:15:25 EST 
No reproducer