Comment 3 for bug 213053

I can also confirm this behavior.
I have tried to remake the behavior that used 100% of the CPU, but couldn't. When it was eating the process power, I did a CTRL ALT BACKSPACE and logged back in again, but it didn't help, I had to restart the computer to kill the process. I didn't find this bug until I restarted so I can't really give any technical data. I have some ideas what caused it though, I hope it may help.
1. When I tried to kill the process it had a very long name with a lot of %s and numbers, not the "real" folder name of the movie (though the English part was spelled right). The movie was Korean and the Korean letters on my folder is " ¤س¤ÃÙÎ͵ ¼ÁÍÂҡ¡ʹ¤ÃѺ" probably because I don't have Korean language installed.
2. This only happens on longer movies for me, after around 1 hour.
3. This movie was from a VCD copied to the computer, so called a .dat file.

My first thoughts after seeing these posts are that none who had the bug has an English last name, and maybe the process name or link (I'm quite a noob) in other than an English language doesn't correspond to the actual folder and it can't kill it if it can't find it. I wish I had taken a screen shot of the process weird extended name, if I encounter this again, I'll send you one.

I hope this could clear up a bit.

Good luck people!