Eclipse: "Update SVN cache" hangs and locks up

Question

Every time I start eclipse, the program begins doing this "Update SVN cache" thing but it will sit at 0% forever. I cannot perform any operations (such as checking out my projects, building them, or even running them) until this operation is completed (which never happens). Also, whenever I try to type anything in the editor, the whole program freezes and I have to kill the process.

I have been searching google for the answer to this problem for days and have yet to come up with an answer. Has anyone else had a similar problem and found a solution?

I'd like to add that I've tried re installing eclipse, all its plugins, and the jdk from scratch. Nothing seems to be working.

Answer 1

I found an index error in eclipse which blocking the svn. Another project resources and svn repo were in .metadata\.plugins\org.eclipse.core.resources\.projects\ProjectName\4.tree and other resources.

svn cleanup with the previous answer with 'Team > SVN > Performance' doesn't solve my problem.

'eclipse.exe -clean' will make eclipse unresponsible with 100% cpu.

The only solution was after exit eclipse the manual deleting of org.eclipse.core.resources\.projects\* files.

Answer 2

I faced the same issue and I tried to get out of this by disable most of performance setting for SVN in Eclipse:

• Windows > Preferences > Team > SVN > Performance

OR (for latest versions): Windows > Preferences > Version Control (Team) > SVN > Performance

• Disable: Computing deep outgoing state, Cache, persistent SSH

Answer 3

I was also facing similar issue and I got it resolved this by unchecking "Compute deep outgoing state for folders" under Windows->Preferences->Team->SVN->Label Decorations

Answer 4

In my case I realized that a tortoise SVN explorer related windows was somewhere open. It probably locked the cache and eclipse was waiting for the unlock.

Not a direct answer to the question, but this might help for somebody making a similar mistake.

Answer 5

I solved doing this:

-Select the project (or all projects) on your workspace (in eclipse), right click, select from the menu Team > Cleanup

Answer 6

1. Windows > Preferences > Team > SVN > Performance
   • Disable: Computing deep outgoing state, Cache, persistent SSH
2. Go to Preference -> General
   • Enable : Always run in background
   • Enable : Show heap status
   • Workbench Save interval (in minutes):9999
   • This will show your memory usage in eclipse.
3. Then edit your eclipse.ini file and change Xms and Xmx values to these: -launcher.XXMaxPermSize 512m -Xms1024m -Xmx1024m

Answer 7

This topic helped me for solving the problem about my eclipse svn update block.

I am using eclipse mars where this case came.

1. First I have deleted two projects which I don't needed - to reduce the project number in the workspace.
2. Changing parameter in eclipse.ini has not helped too.
3. I had the -clean argument on my eclipse set so I have deleted that too in hope it will work better. It helped a bit so the eclispe was running much longer but not much more. rockfarkas hint here.
4. What really helped at the end was to mark very fast all projects CtrlA from the project view and close them via the context menu while the SVN cache was still running. The half of them did that the others couldn't but after that I could see that the SVN cache was changing its state and so I could work again. The next step was to close the rest of the projects and open one by one. To this idea I came reading the post of user3096856.

Answer 8

I used Subversive - SVN Team Provider 3.0.0 with SVNKit 1.8.10 as SVN Connctor. I updated the SVN Connctor to the latest version 1.8.11,and fixed it.

Answer 9

It could be eclipse memory issue. I had similar problem until I did these steps:

• Go to Preference -> General and put these values:

This will show your memory usage in eclipse.

• Then edit your eclipse.ini file and change Xms and Xmx values to these:

-Xms1024m

-Xmx1024m

Look at the memory status. Hope it will help.

Answer 10

If there is duplicate project from SVN.

1. Force close eclipse.
2. Delete the duplicate project from filespace. (Eg: C:\Users\XXX\Workspace\DuplicateProject)
3. Restarting the eclipse
4. fixed.

Answer 11

I faced this problem when having the same project in the workspace twice. Make sure you have only one copy of it in the workspace, maybe it helps.

Answer 12

Do you use Maven SCM connector ? Try uninstalling it if you dont need it. SCM connector is required for Maven SCM checkout, I do not use Maven SCM project checkout, instead I use SubEclipse checkout and convert project to maven using import existing project or convert to Maven project option from the context menu in Eclipse.

Answer 13

I just ran into this issue and was able to rescue it. This was with Zend Studio 10.5 which sits on Juno. I have about five projects in my workspace, one of which was open. I couldn't close the project because it was waiting for "Update SVN Cache" to complete.

• With Eclipse closed, I went to my open project and via the command line ran "svn cleanup."
• In workspace/.metadata/.plugins/org.eclipse.team.svn.core, I had a bunch of temp directories. I created a backup tarball, and then blew them all away.

That didn't fix anything. Finally I tried this:

1. With Eclipse closed, I went to my project directory and renamed .project to project.xml.
2. Reopened Eclipse, projects were closed. No SVN Update messages.
3. Restarted Eclipse.
4. Opened the project, but Eclipse balked at the missing .project file.
5. Closed Eclipse.
6. Went to my project directory and renamed project.xml back to .project.
7. Restarted Eclipse.
8. Opened the project. Smooth sailing. Was just able to commit a change without incident.

So far my workspace/.metadata/.plugins/org.eclipse.team.svn.core directory is still empty.

I don't know if the first two things I tried helped out at all, or if just renaming the .project file to force-close the project was all it took. Next time it happens (and there will be a next time) I'll try just force-closing the project and report back.

Answer 14

In my case, for 30 odd minutes it showed just 0 percent completed. I patiently waited since I tried restarting eclipse/machine still was getting the same thing. After 30 minutes, it continued with my svn update operation and completed it successfully.

Patience at times, helps :)

Answer 15

You're not the only one (see this bug report or this forum thread) but it's probably not a bug in Eclipse itself. Next steps:

1. Get a thread dump to see whether this is a deadlock or a thread is waiting for something that never happens (in the bug report, it hangs in System.loadLibrary()). You can use jconsole for this, it comes with the SDK.

2. Check all open projects in your workspace (that use SVN) with another SVN tool (command line svn or TurtoiseSVN if you're on windows) to make sure the data structures aren't corrupt.

3. Get the latest version of Eclipse and/or the SVN plugin

4. Try a different connector. Some people fare better with the JNI solution javahl, others with the pure-Java SVNKit.