Hi, I cannot reproduce the issue -- in fact, I came across it on the bugs.debian.org website which is encoded in UTF-8 so it cannot represent the non-UTF-8 you're talking about. I'm copy-pasting the command but it's perfectly valid UTF-8 and no lockup happens. It would be great if you could construct a command line that emits such locking non-UTF-8 (e.g. echo "\x12\x34..."), whereas the command itself can be copy-pasted from UTF-8 websites.
That being said, I suspect that this bug might be the same as (or similar to) https://bugzilla.xfce.org/show_bug.cgi?id=13383 https://bugzilla.gnome.org/show_bug.cgi?id=777733 https://bugzilla.gnome.org/show_bug.cgi?id=730154 comments 4-7 although that wouldn't explain the 100% CPU usage. cheers, egmont
