Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 29329

Summary: [Decorators] Bug in 3rd party plugin crashes view
Product: [Eclipse Project] Platform Reporter: Ron Baldwin <bogofilter+eclipse.org>
Component: UIAssignee: Tod Creasey <Tod_Creasey>
Status: RESOLVED DUPLICATE QA Contact:
Severity: normal    
Priority: P3    
Version: 2.1   
Target Milestone: ---   
Hardware: PC   
OS: Windows 2000   
Whiteboard:
Attachments:
Description Flags
.log file none

Description Ron Baldwin CLA 2003-01-10 21:33:36 EST 
Create a new workspace.  Add a project that already has a .project file with the
"org.vssplugin.core.VSSPluginProvider" nature (from
http://sourceforge.net/projects/vssplugin/).  Eclipse gives you an error:
"Unable to create part: Package Explorer".  I assume this is because the plug-in
does not correctly handle missing configuration (since we started with a new
workspace).  Package Explorer will continue to return errors when you open it
until you take the offending <nature> line out of the .project file.  Instead of
bombing the view, Eclipse should probably disable the nature on the project (for
the running instance of Eclipse) and ask the user if they want the nature
removed from the .project file.  The .log file is attached.
Comment 1 Ron Baldwin CLA 2003-01-10 21:34:21 EST 
Created attachment 2951 [details]
.log file
Comment 2 Dirk Baeumer CLA 2003-01-13 06:08:00 EST 
The stack trace shows that the problem is caused during label decoration. May 
be platform should disable label decoration if the corresponding extension 
point causes an exception.

Moving to Platform for commenting.
Comment 3 Tod Creasey CLA 2003-01-13 12:54:29 EST 
As of build 20030114 decorators are now thread safe (see Bug 28134). The view 
will no longer crash - you will just let a lot of errors written to your log. 
We considered turning off the decorators in this case but it turned out to be 
a difficult concurency problem for a small payoff - see Bug 29046.

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