Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 55870 - Eclipse hangs while working with markers after a build workspace
Summary: Eclipse hangs while working with markers after a build workspace
Status: RESOLVED DUPLICATE of bug 55605
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Team (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows 2000
: P3 critical (vote)
Target Milestone: ---   Edit
Assignee: Platform Team Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-03-24 07:35 EST by Frederic Fusier CLA
Modified: 2004-03-24 11:00 EST (History)
1 user (show)

See Also:


Attachments
VM Snapshots while hanging... (168.74 KB, text/plain)
2004-03-24 07:37 EST, Frederic Fusier CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Frederic Fusier CLA 2004-03-24 07:35:15 EST
Using build I200403230800.

My compiler options makes me having more than 20,000 warnings (I have javadoc 
and unqualified filed access option activated :(().
Of course I do not display all of them in Problems view but have set a filter 
just to display errors.

So, the problem view is empty... But since I've installed this new M8 candidate 
build, my workspace is unusable as each time there's a rebuild of the 
workspace, eclipse hangs looping infintely in markers areas as will show the VM 
snapshots I'll attach to this bug...
Comment 1 Frederic Fusier CLA 2004-03-24 07:37:41 EST
Created attachment 8821 [details]
VM Snapshots while hanging...
Comment 2 Tod Creasey CLA 2004-03-24 09:25:46 EST
This blockage is caused by the sync view calculation markers in the UI Thread
(see trace below). I think this may have been fixed in the test build

main" prio=7 tid=0x00235db0 nid=0xb8c waiting on condition [6e000..6fc3c]
        at java.util.ArrayList.ensureCapacity(ArrayList.java:169)
        at org.eclipse.core.internal.resources.MarkerManager.buildMarkers
(MarkerManager.java:163)
        at org.eclipse.core.internal.resources.MarkerManager$3.visitElement
(MarkerManager.java:493)
        at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration
(ElementTreeIterator.java:76)
        at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration
(ElementTreeIterator.java:80)
        at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration
(ElementTreeIterator.java:80)
        at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration
(ElementTreeIterator.java:80)
        at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration
(ElementTreeIterator.java:80)
        at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration
(ElementTreeIterator.java:80)
        at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration
(ElementTreeIterator.java:80)
        at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration
(ElementTreeIterator.java:80)
        at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration
(ElementTreeIterator.java:80)
        at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration
(ElementTreeIterator.java:80)
        at org.eclipse.core.internal.watson.ElementTreeIterator.iterate
(ElementTreeIterator.java:119)
        at org.eclipse.core.internal.resources.MarkerManager.visitorFindMarkers
(MarkerManager.java:498)
        at org.eclipse.core.internal.resources.MarkerManager.findMarkers
(MarkerManager.java:218)
        at org.eclipse.core.internal.resources.Resource.findMarkers
(Resource.java:777)
        at 
org.eclipse.team.internal.ui.synchronize.SynchronizeModelProvider.propagateProb
lemMarkers(SynchronizeModelProvider.java:455)
        at 
org.eclipse.team.internal.ui.synchronize.SynchronizeModelProvider.calculateProp
erties(SynchronizeModelProvider.java:440)
        at 
org.eclipse.team.internal.ui.synchronize.SynchronizeModelProvider$7.run
(SynchronizeModelProvider.java:563)
        at org.eclipse.swt.custom.BusyIndicator.showWhile
(BusyIndicator.java:84)
Comment 3 Frederic Fusier CLA 2004-03-24 09:59:26 EST
I agree. This problem does no longer occur with build 200403240010.
Thanks
Comment 4 Jean-Michel Lemieux CLA 2004-03-24 11:00:37 EST

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