I'm not sure if it has been reported already :
A SVM commit take 90% of my core duo proc.
It is very long and look like frozen.
An authentication error can be seen but a user/password had been asked and the commit had started.
There must be something wrong in the code with all that CPU taken.
After having cancelled it look like the commit had been done.
Of course, I doubt...
I then tested a checkout and it also took too much CPU.
At the end, it is painfull to use.
Message was edited by: