Continuous high CPU usage with 1.5.2
My main PC, Windows 7 Pro 64-bit, is wired to 1 Sony player, another connects via wifi. Processor is an AMD FX-8320 8-core. The 2nd PC is older, WinXP SP 3, processor is AMD Phenom II X2 550 2-core and uses wifi to play movies and connect to both Sony players (BDP-S5100 and S5200).
Since upgrading to 1.5.2 though, both PCs will eventually just stop doing anything until I force-stop Serviio, because ServiioServer.exe is using up to 98% of the CPU. This happens on a fresh reboot, start up the server and console, and never starting either of the players at all. So there's not even any movie viewing or transcoding that's been done that might continue happening in the background, there should be nothing but updates to the library if necessary. I have all online metadata retrieval turned off. But within 2 hours or so CPU usage will be at the 98% point for Serviio.
I've tried completely uninstalling Serviio and reinstalling it several times on both PCs, no change. I've added Serviio to be excluded from my AV program, even tried it with AV turned completely off. I've tried removing any networked drives from the library, again no change. I've tried setting the library to update manually only, no change.
Last week I finally decided to try and go back to 1.4.1.2 on the WinXP machine (I know that version was working well on both PCs) to test it, and CPU usage for Serviio generally stays at 0% and might get to 10% if updating the library for a very short time only, then go back down to 0%. Even when viewing movies it never gets very high at all even while transcoding, and drops back to 0 CPU when not in use. The problem instantly went away by downgrading.
I kept 1.5.2 on the Windows 7 PC for now hoping to figure out why Serviio is doing this. The attached log was taken over a few hours where I was checking the CPU quite often. Serviio was started up at 10:13 am. CPU was still at 0% as 12:04 pm, but at 12:17 pm I noticed it was at 70% so hopefully that helps pin down the time when whatever causes it began. I deleted most entries before 12:04 to keep the file size down to the allowed limit.