Bug 314072 - Acquiring EclipseSynchronizer lock can cause RuntimeException logged from ColumnViewer
Summary: Acquiring EclipseSynchronizer lock can cause RuntimeException logged from Col...
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Team (show other bugs)
Version: 3.6   Edit
Hardware: PC Linux-GTK
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform Team Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-24 04:49 EDT by James Blackburn CLA
Modified: 2019-09-06 15:30 EDT (History)
0 users

See Also:

Attachments
back trace (5.79 KB, text/plain)
2010-05-24 04:49 EDT, James Blackburn CLA 		no flags Details
View All 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 James Blackburn CLA 2010-05-24 04:49:13 EDT 
Created attachment 169643 [details]
back trace

A user saw this in an error log in 3.6RC1

It looks like the Viewer is being refreshed while an existing refresh is underway as a result of doPendingWork while trying to acquire the EclipseSynchronizer lock.

Looking at the code the error is only logged once. Not sure of the best category for this but team seems to be involved in both refreshes...

(Note that line numbers of CVSLightweightDecorator is different from HEAD, but trivial changes are in methods not in this stackdump. All other team and CVS classes are as on RC1.)
Comment 1 Eclipse Webmaster CLA 2019-09-06 15:30:16 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.