Bugzilla – Bug 345
mov123.exe causes a large CPU spike at startup
Last modified: 2008-12-18 11:50:52 UTC
Subject: [slim] Pause after track change with multiple Squeezeboxes using Apple Lossless Date: Thu, 3 Jun 2004 19:52:35 +0100 From: Jon Webber <jon.webber@dsl.pipex.com> I have two Squeezeboxes. I'm streaming Apple Lossless to both of them. When I have both running with separate tracks things are fine until I skip to another track on one unit. This causes the music to pause on the other squeezebox. On investigation this is because the mov123.exe file takes up about 80-90% of CPU for a short burst (I'm guessing while it loads in the Lossless file?), thus affecting the other stream. I'm running this on an old Pentium II PC 400Mhz, with 380 RAM. I've also tried it on my relatively new AMD 2600 PC with 1 Gb of RAM, and mov123.exe occasionally gets up to the 60% CPU mark, sometimes causing the other player to pause in a similar fashion. Is there anything that can be done in mov123.exe to soften this peak of CPU activity? or can you suggest I try something else to fix the problem.
Well I have to take that back. When initially starting the slimserver, the CPU usage is low. But after some period of time (hours I think), regardless of whether any music is playing, the CPU usage builds back up and the squeezebox and server response gets slow again. What should I do to track down the problem further?
Routine bug db maintenance; removing old versions which cause confusion. I apologize for the inconvenience.