I use SmartSVN as my GUI front-end for using subversion repositories on the web. In my case, I'm using SmartSVN to maintain the page for the JDK7 project at jdk7.dev.java.net. I tried to switch from using JDK-1.6.0 as my JVM to using JDK-1.7.0-ea-b23. Most things worked fine, as one would expect moving from one release of the JDK to the next. But when I tried to commit a change, the application seemed to hang. But instead of being hung, it was using 100% of my CPU's.

I attached jconsole to the process and poked at the threads to see which one was running away with the machine. It seems to be the AWT-EventQueue-0 thread. I grabbed 5 thread stack dumps at random intervals, hoping that would give you a clue as to what's going on. I've attached them to this bug report. I was not doing anything in the window that was SmartSVN: I was only clicking in the jconsole threads tab.

I'm running on a SunBlade2500 running Solaris 10. I haven't tried reproducing the problem on any other platforms, but I could if you need me to. This bug reproduces every time. I don't have a "practice" subversion repository against which to make random changes, so I have to make changes that I'd be willing to actually commit to the jdk7.dev.java.net project pages, but that's not that inconvenient. I don't have any reason to suspect that what I'm committing or where I'm committing it to makes any difference to the bug.

SmartSVN is available at http://www.syntevo.com/smartsvn/download.html. I'm using the "Generic (Linux, Unix, OS/2)" version 3.0.4, but I first noticed the problem with their 2.1.7.