* git gui blame: git-blame loops at 100% cpu
@ 2010-04-17 23:13 Konrad Karl
2010-04-18 21:52 ` Konrad Karl
2010-04-18 21:52 ` Konrad Karl
0 siblings, 2 replies; 3+ messages in thread
From: Konrad Karl @ 2010-04-17 23:13 UTC (permalink / raw)
To: git
Dear list,
I have converted one of our Visual Source Safe repos to git (about 47000 commits, about 11 years of history, .git about 200 MB git gc'ed).
Everything seems to be working fine but git gui blame some_file seems to
procedure correct output in the file viewer but the progress bar stops
at 1271 of 2783 lines for one specific file and then the git-blame process
consumes 100% cpu.
Plain git blame completes in a fraction of a second just fine.
git-1.7.0.1-1.fc13.x86_64 (Fedora 13). I have also tested git 1.7.0.5
- same behaviour. ditto for the latest msys git in Windows.
perhaps I should mention that most of the source files in the repo are
using crlf line endings.
The hang does not happen on all files but on many - progress percentage
varying.
Konrad
--
Sicherer, schneller und einfacher. Die aktuellen Internet-Browser -
jetzt kostenlos herunterladen! http://portal.gmx.net/de/go/atbrowser
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: git gui blame: git-blame loops at 100% cpu
2010-04-17 23:13 git gui blame: git-blame loops at 100% cpu Konrad Karl
@ 2010-04-18 21:52 ` Konrad Karl
2010-04-18 21:52 ` Konrad Karl
1 sibling, 0 replies; 3+ messages in thread
From: Konrad Karl @ 2010-04-18 21:52 UTC (permalink / raw)
To: git
Replying to myself
> Everything seems to be working fine but git gui blame some_file seems to
> procedure correct output in the file viewer but the progress bar stops
> at 1271 of 2783 lines for one specific file and then the git-blame process
> consumes 100% cpu.
Grr, this was a false alarm. It finishes after about 4 Minutes and I
did not wait that long. git gui was using git-blame -C -C40.
gui.fastcopyblame=true seems to help to get sane runtimes.
(this can be achieved by checkin "Blame Copy Only On Changed Files"
in git gui options dialog -kudos to charon in #git for this suggestion)
Perhaps this should be made the default?
Konrad
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: git gui blame: git-blame loops at 100% cpu
2010-04-17 23:13 git gui blame: git-blame loops at 100% cpu Konrad Karl
2010-04-18 21:52 ` Konrad Karl
@ 2010-04-18 21:52 ` Konrad Karl
1 sibling, 0 replies; 3+ messages in thread
From: Konrad Karl @ 2010-04-18 21:52 UTC (permalink / raw)
To: git
Replying to myself
> Everything seems to be working fine but git gui blame some_file seems to
> procedure correct output in the file viewer but the progress bar stops
> at 1271 of 2783 lines for one specific file and then the git-blame process
> consumes 100% cpu.
Grr, this was a false alarm. It finishes after about 4 Minutes and I
did not wait that long. git gui was using git-blame -C -C40.
gui.fastcopyblame=true seems to help to get sane runtimes.
(this can be achieved by checkin "Blame Copy Only On Changed Files"
in git gui options dialog -kudos to charon in #git for this suggestion)
Perhaps this should be made the default?
Konrad
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2010-04-18 21:52 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-04-17 23:13 git gui blame: git-blame loops at 100% cpu Konrad Karl
2010-04-18 21:52 ` Konrad Karl
2010-04-18 21:52 ` Konrad Karl
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.