git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: git gui blame: git-blame loops at 100% cpu

From
KKKonrad Karl <kk_konrad@gmx.at>
Date
Apr 18, 2010, 21:52 UTC
Message-ID
<21951.1431911544$1271627542@news.gmane.org>
In-Reply-To
<20100417231327.162560@gmx.net>
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
Previous: Konrad KarlNext: Konrad Karl
Message 2 of 3 in “git gui blame: git-blame loops at 100% cpu”
  1. Konrad KarlApr 17, 2010
  2. Konrad KarlApr 18, 2010
  3. Konrad KarlApr 18, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.