Tom Ellis Huckstep <[EMAIL PROTECTED]> writes: > This sounds like something to do with the PID file not being removed > properly. Can you reproduce this bug?
I've only seen polipo get itself into that state once. I had the web browser on one machine pointed at a polipo on another machine on the LAN and was trying to watch a video on youtube.com. I stopped the video when it was partially downloaded, and that's when polipo started using a lot of CPU. I've since stopped using polipo, but will start again to see if I can provoke it to do the same thing again. While it was using a lot of CPU, I attached to it with 'strace', but it wasn't doing any system calls at all. I then tried attaching to it with gdb, but that produced a useless stack trace. I was expecting that when I quit gdb, the CPU usage would go straight back up again as polipo resumed doing whatever it was doing, but that didn't happen for 10 or 20 seconds. I tried a 'kill $PID' and 'kill -HUP $PID', but neither killed the polipo process. Finally, a 'kill -KIPP $PID' killed it. After that I could start a new polipo process. I'll report back if and when I've reproduced the problem. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
