{"thread":{"id":"27920","subject":"weird performance bug","startedAt":"2011-07-25T23:03:52Z","lastAt":"2011-07-25T23:03:52Z","messageCount":1,"participants":["fREW Schmidt"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"172026","messageId":"CADVrmKQ5YU9qBVT_Xi1GcGr8PRzyLzHCsA2bHqzmrvtCXw9JEg@mail.gmail.com","threadId":"27920","inReplyTo":null,"subject":"weird performance bug","fromName":"fREW Schmidt","fromEmail":"frioux@gmail.com","sentAt":"2011-07-25T23:03:52Z","receivedAt":"2011-07-25T23:03:52Z","isPatch":false,"sender":{"key":"frioux@gmail.com","avatar":"https://gravatar.com/avatar/639ef3cc221c7f2c225568697bc9d42be4d4e3bada6b4a3b9c32685548f3c105?d=mp&s=160"},"body":"I'm not really sure how to reproduce this without sharing my whole\nrepo so I'll explain it first.\n\nI did a fairly large merge today at work and in the process, so that I\ncould skim some stuff, I set gitk to have zero lines of context.\nAfter finally committing the merge, if I ran gitk, it would consume an\nentire core trying to (I'm guessing) render the diff for gitk.  It\nnever completed, and even after closing gitk, there was still a git\nprocess in the background pegging a core.  If I fix the lines of\ncontext to be 3 again and restart gitk the problem goes away.\n\nThis occurred on ubuntu with git 1.7.6.\n\n--\nfREW Schmidt\nhttp://blog.afoolishmanifesto.com\n"}]}