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

Bug 321542

Summary: FileReplaceListener performs time consuming actions at inappropriate time
Product: [Technology] Subversive Reporter: John Kristian <jmkristian>
Component: CoreAssignee: Igor Burilo <igor.burilo>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: P3 CC: dimitri, heiko.boettger, jmkristian
Version: 0.7   
Target Milestone: ---   
Hardware: Macintosh   
OS: Mac OS X - Carbon (unsup.)   
Whiteboard:
Bug Depends on:    
Bug Blocks: 287559    
Attachments:
Description Flags
thread dump from jvisualvm
none
thread dump 2 from jvisualvm
none
CPU profile snapshot none

Description John Kristian CLA 2010-08-02 21:35:58 EDT
Build Identifier: 20100617-1415

From time to time, Eclipse will stop responding to the user interface.  The progress indicator shows 'Building workspace: (0%)'.  The process uses roughly 1 CPU (out of 8).

This doesn't happen every time it builds the workspace.

The workspace contains a fairly large project, with more than a thousand source directories. It was imported and shared using Subversive.

I'll attach two thread dumps, taken using jvisualvm, and a CPU profile snapshot from YourKit.

Reproducible: Sometimes
Comment 1 John Kristian CLA 2010-08-02 21:37:42 EDT
Created attachment 175737 [details]
thread dump from jvisualvm
Comment 2 John Kristian CLA 2010-08-02 21:38:11 EDT
Created attachment 175738 [details]
thread dump 2 from jvisualvm
Comment 3 John Kristian CLA 2010-08-02 21:58:08 EDT
Created attachment 175739 [details]
CPU profile snapshot

The attached snapshot was taken by YourKit Java Profiler 9.0.7, using CPU tracing (not sampling).  It indicates that at least 53% of the CPU time was used to execute SVNRemoteStorage.asLocalResource and the methods it calls.
Comment 4 Alexander Gurov CLA 2011-06-17 12:09:33 EDT
Current solution for bug #276018 is completely inappropriate, which is the real cause of the problem. So, for now the listener is removed and corresponding bug is reopened with detailed description as to how to solve the problem.
Comment 5 Alexander Gurov CLA 2011-11-14 05:37:53 EST
*** Bug 325215 has been marked as a duplicate of this bug. ***