From: "Konrad Karl" <kk_konrad@gmx.at>
To: git@vger.kernel.org
Subject: git gui blame: git-blame loops at 100% cpu
Date: Sun, 18 Apr 2010 01:13:27 +0200 [thread overview]
Message-ID: <20100417231327.162560@gmx.net> (raw)
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
next reply other threads:[~2010-04-17 23:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-17 23:13 Konrad Karl [this message]
2010-04-18 21:52 ` git gui blame: git-blame loops at 100% cpu Konrad Karl
2010-04-18 21:52 ` Konrad Karl
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100417231327.162560@gmx.net \
--to=kk_konrad@gmx.at \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).