2013-02-21, 02:08
(2013-02-20, 22:22)cfetzer Wrote: Thanks a lot for that clarification. I had to ask, just to make sure under all circumstances that we won't end up fixing something at the wrong end.
And if you see improvements, we probably have found the wrongly behaving component already.
1-2. It's good to know, that the addon causes in general a bit higher cpu load on the backend. Think might be related to several things and is most likely really difficult to solve. It could be due to different buffer sizes, different usage of the mythtv protocol, timings, ...
I agree, it's an issue, but low prio for now.
3. Ok then janbar's last patch optimized things in our image cacheing component and indeed seems to have an influence on the increased load.
Could you check if you see MythSocket errors in the backend log? If so, it might help if you could enable debug logging in the addon and post logs of both, backend and xbmc, for the timeranges where you see the socket errors.
Here you go. At 17:24:43, I see
Feb 20 17:24:43 MythTV mythlogserver: mythbackend[2088]: W ProcessRequest mainserver.cpp:5841 (connectionClosed) MainServer: Unknown socket closing MythSocket(0x9e2add0)
It seems to have occurred while the PVR manager was still starting up.
Here is the full log:
http://pastebin.com/3Legb0Wx
And the XBMC debug log (which seems to be too big for pastebin):
https://docs.google.com/file/d/0B5684fzv...sp=sharing