{"thread":{"id":"23504","subject":"git gui blame: git-blame loops at 100% cpu","startedAt":"2010-04-17T23:13:27Z","lastAt":"2010-04-18T21:52:10Z","messageCount":3,"participants":["Konrad Karl"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"139792","messageId":"20100417231327.162560@gmx.net","threadId":"23504","inReplyTo":null,"subject":"git gui blame: git-blame loops at 100% cpu","fromName":"Konrad Karl","fromEmail":"kk_konrad@gmx.at","sentAt":"2010-04-17T23:13:27Z","receivedAt":"2010-04-17T23:13:27Z","isPatch":false,"sender":{"key":"kk_konrad@gmx.at","avatar":null},"body":"Dear list,\n\nI 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). \n\nEverything seems to be working fine but git gui blame some_file seems to\nprocedure correct output in the file viewer but the progress bar stops \nat 1271 of 2783 lines for one specific file and then the git-blame process\nconsumes 100% cpu. \n \nPlain git blame completes in a fraction of a second just fine.\n\ngit-1.7.0.1-1.fc13.x86_64 (Fedora 13). I have also tested git 1.7.0.5\n- same behaviour. ditto for the latest msys git in Windows.\n\nperhaps I should mention that most of the source files in the repo are\nusing crlf line endings.\n\nThe hang does not happen on all files but on many - progress percentage \nvarying.\n\nKonrad\n\n\n-- \nSicherer, schneller und einfacher. Die aktuellen Internet-Browser -\njetzt kostenlos herunterladen! http://portal.gmx.net/de/go/atbrowser\n"},{"id":"139851","messageId":"21951.1431911544$1271627542@news.gmane.org","threadId":"23504","inReplyTo":"20100417231327.162560@gmx.net","subject":"Re: git gui blame: git-blame loops at 100% cpu","fromName":"Konrad Karl","fromEmail":"kk_konrad@gmx.at","sentAt":"2010-04-18T21:52:10Z","receivedAt":"2010-04-18T21:52:10Z","isPatch":false,"sender":{"key":"kk_konrad@gmx.at","avatar":null},"body":"Replying to myself\n\n> Everything seems to be working fine but git gui blame some_file seems to\n> procedure correct output in the file viewer but the progress bar stops \n> at 1271 of 2783 lines for one specific file and then the git-blame process\n> consumes 100% cpu. \n\nGrr, this was a false alarm. It finishes after about 4 Minutes and I\ndid not wait that long. git gui was using git-blame -C -C40.\n\ngui.fastcopyblame=true seems to help to get sane runtimes.\n(this can be achieved by checkin \"Blame Copy Only On Changed Files\"\n in git gui options dialog -kudos to charon in #git for this suggestion)\n\nPerhaps this should be made the default?\n\nKonrad\n"},{"id":"299244","messageId":"20100418215210.GA19776localhost","threadId":"23504","inReplyTo":"20100417231327.162560@gmx.net","subject":"Re: git gui blame: git-blame loops at 100% cpu","fromName":"Konrad Karl","fromEmail":"kk_konrad@gmx.at","sentAt":"2010-04-18T21:52:10Z","receivedAt":"2010-04-18T21:52:10Z","isPatch":false,"sender":{"key":"kk_konrad@gmx.at","avatar":null},"body":"Replying to myself\n\n> Everything seems to be working fine but git gui blame some_file seems to\n> procedure correct output in the file viewer but the progress bar stops \n> at 1271 of 2783 lines for one specific file and then the git-blame process\n> consumes 100% cpu. \n\nGrr, this was a false alarm. It finishes after about 4 Minutes and I\ndid not wait that long. git gui was using git-blame -C -C40.\n\ngui.fastcopyblame=true seems to help to get sane runtimes.\n(this can be achieved by checkin \"Blame Copy Only On Changed Files\"\n in git gui options dialog -kudos to charon in #git for this suggestion)\n\nPerhaps this should be made the default?\n\nKonrad\n"}]}