Crashing bug
By fla... on January 12, 2011 17:13 (imported from Google Code)
I was ssh'ed into a remote box, and had run a script which accidentally "curl"'ed a tarball to stdout, causing the usual blast of "binary" characters to the console.
I tried to Ctrl-C to abort the script, iTerm2 ended up crashing out with this report:
https://gist.github.com/776472
If I were to guess, some string of bytes in the tarball was interpreted as a multibyte character in some odd way; looks like a crash during text rendering at any rate.