One thing that concerns me though is the CPU usage on the client machine. chromium uses roughly ~30% CPU on a 6-core AMD Phenom II running only zmusic. Anyone else seeing this too?
That's quite astounding, yikes. I have less than 1 percent of CPU usage with my Chromium. (Using latest dev channel, built from scratch with -march=native -O2 -fomit-frame-pointers -pipe.)
If there's high CPU usage, file a Chrome bug -- it's possibly do to some nastiness in their audio decoder.
Found out that it seems to be the drawing of the progress bar, as weird as that may sound. When I switch to another tab, the CPU usage drops. I'm on Linux using the open source ATI radeon driver, that might have something to do with it.
Well that's quite interesting... Try and see if it still happens with fglrx. The progress bar is a CSS3 animation, which means Chromium likely hardware accelerates it, so I could imagine buggy drivers causing issues.
One thing that concerns me though is the CPU usage on the client machine. chromium uses roughly ~30% CPU on a 6-core AMD Phenom II running only zmusic. Anyone else seeing this too?