I'm working on my own local web server. If I stream from my web server to fb2k (via loopback), then kill the server while fb2k is still streaming, fb2k will play all the data it got before the socket closed then start chewing 100% of the CPU. If I press the fb2k's stop button, it stops doing so and the CPU use dies down. I don't know how bad the spinning is for single-core folks; I've got a dual-core machine, and it never becomes unusable.

This is with fb2k v0.9.4.2.

Cheers,


larry