Description Ayushman Jain 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.