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

Bug 359422

Summary: Git Staging view hogs all system resources when unstaged resource is deleted
Product: [Technology] EGit Reporter: Ayushman Jain <amj87.iitr>
Component: UIAssignee: Project Inbox <egit.ui-inbox>
Status: CLOSED WORKSFORME QA Contact:
Severity: normal    
Priority: P3 CC: emoffatt, loskutov, remy.suen, xmedeko
Version: 1.1   
Target Milestone: ---   
Hardware: All   
OS: All   
Whiteboard:

Description Ayushman Jain CLA 2011-09-29 09:30:19 EDT 
With 23 September's nightly build, I managed to make Git staging view eat up 100% CPU cycles. Here's what happened (ensure Git staging is open):

1) Create a resource in the directory where your local repo is stored. (I created a patch which got saved in C:\Documents and Settings\Administrator\git\eclipse.jdt.core).
2) The resource is shown in the unstaged changes in the git staging view. I saw this is a distraction, and not knowing how to remove it from inside of Eclipse, manually deleted the resource from the file system.
3) Git staging view removed the resource, but started an indexing job which hogged CPU cycles.
Comment 1 Ondrej Medek CLA 2012-03-12 10:39:40 EDT 
I have no problem with that in EGit 1.3.0.201202151440-r. Can you try it again with the newest EGit stable version?
Comment 2 Andrey Loskutov CLA 2015-08-14 09:22:08 EDT 
Using 4.1 I don't see the issue - probably we've fixed it somewhere between 1.1 and 4.0 :-)