2013-03-03, 15:39
(2013-03-03, 10:20)cfetzer Wrote:(2013-03-02, 17:22)richardk Wrote: OpenELEC 2.99.4 (RC4) was released yesterday. Unfortunately, it still has version 1.6.7 of the addon.
If the latest changes don't make it into the final release of OpenELEC with Frodo, there are going to be a lot of unhappy users.
I don't know the details of how the distribution process works, but it seems that it needs some streamlining so that fixes can get out to users when they are needed.
Do you have any contacts in openelec? I asked on their irc channel but didn't get an answer.
In general, we release our stuff to the official xbmc repo github.com/opdenkamp/xbmc-pvr-addons but when the release is rolled out to the users
is no more in our hands. For linux it's up to the distribution authors to pick the changed from there.
Other platforms should get the update installed at some point. Which hasn't happened so far.
I try to write as much info as possible in our change log, so it should be clear for distro maintainers that it's worth to pick that update.
---
About the cpu load:
Since I still cannot reproduce the issue, I've queued a lot more recordings now and in addition I'm using munin and the proc plugin to gather statistics on the mythbackend process.
It'll create graphs about CPU and memory usage, number of threads and a couple of more things.
I will let it run for a couple of days now without restarting and hopefully that helps to find out why the cpu load increases.
If you have the issue, could you check if there is an inexplicable high number of tcp connections between xbmc and the backend?
Code:sudo netstat -apn | grep mythbackend
In addition I'm working on aligning the tcp receive buffer sizes. It could be related to the problem: https://github.com/fetzerch/xbmc-pvr-addons/pull/98
It's not yet ready for testing since it causes stuttering. I'll let you know as soon as there's something to test.
One interesting thing would be: Do we have anybody here that has the increasing cpu load issue while using only windows as frontend?
Thanks,
Christian
I'm just another user of OpenELEC, but I'll post something on their forum about the need to update the cmyth addon. It just seems like the process is awkward, since it has to go through several hands before making it out to the users. But I know there's nothing you guys can do about it.
Here is the output you requested. This is with one HD stream playing on XBMC from 192.168.1.83:
Code:
richard@MythTV:~$ sudo netstat -apn | grep mythbackend
[sudo] password for richard:
tcp 0 0 192.168.1.77:6543 0.0.0.0:* LISTEN 17737/mythbackend
tcp 0 0 127.0.0.1:6543 0.0.0.0:* LISTEN 17737/mythbackend
tcp 0 0 192.168.1.77:6544 0.0.0.0:* LISTEN 17737/mythbackend
tcp 0 0 127.0.0.1:6544 0.0.0.0:* LISTEN 17737/mythbackend
tcp 0 0 192.168.1.77:6543 192.168.1.83:39954 ESTABLISHED 17737/mythbackend
tcp 0 0 192.168.1.77:6543 192.168.1.83:46169 ESTABLISHED 17737/mythbackend
tcp 0 0 192.168.1.77:6543 192.168.1.83:46171 ESTABLISHED 17737/mythbackend
tcp 0 0 192.168.1.77:6543 192.168.1.83:40021 ESTABLISHED 17737/mythbackend
tcp 0 0 127.0.0.1:49149 127.0.0.1:35327 ESTABLISHED 17737/mythbackend
tcp 0 0 192.168.1.77:6543 192.168.1.83:46173 ESTABLISHED 17737/mythbackend
tcp6 0 0 fe80::230:67ff:fe3:6543 :::* LISTEN 17737/mythbackend
tcp6 0 0 ::1:6543 :::* LISTEN 17737/mythbackend
tcp6 0 0 fe80::230:67ff:fe3:6544 :::* LISTEN 17737/mythbackend
tcp6 0 0 ::1:6544 :::* LISTEN 17737/mythbackend
udp 0 0 255.255.255.255:1900 0.0.0.0:* 17737/mythbackend
udp 0 0 239.255.255.250:1900 0.0.0.0:* 17737/mythbackend
udp 0 0 0.0.0.0:6549 0.0.0.0:* 17737/mythbackend
unix 3 [ ] STREAM CONNECTED 542732 17737/mythbackend
unix 3 [ ] STREAM CONNECTED 542486 17737/mythbackend
unix 3 [ ] STREAM CONNECTED 542484 17737/mythbackend
unix 3 [ ] STREAM CONNECTED 540647 17737/mythbackend
unix 3 [ ] STREAM CONNECTED 538471 17737/mythbackend
unix 3 [ ] STREAM CONNECTED 540470 17737/mythbackend
unix 3 [ ] STREAM CONNECTED 537964 17737/mythbackend
unix 2 [ ] STREAM CONNECTED 535226 17737/mythbackend
unix 3 [ ] STREAM CONNECTED 530983 17737/mythbackend
unix 3 [ ] STREAM CONNECTED 360166 17737/mythbackend
unix 3 [ ] STREAM CONNECTED 360740 17737/mythbackend
unix 3 [ ] STREAM CONNECTED 359840 17737/mythbackend
unix 3 [ ] STREAM CONNECTED 359838 17737/mythbackend
unix 3 [ ] STREAM CONNECTED 359837 17737/mythbackend
unix 3 [ ] STREAM CONNECTED 360479 17737/mythbackend
unix 3 [ ] STREAM CONNECTED 359810 17737/mythbackend
unix 2 [ ] STREAM CONNECTED 360478 17737/mythbackend
unix 2 [ ] STREAM CONNECTED 359625 17737/mythbackend
unix 3 [ ] STREAM CONNECTED 359272 17737/mythbackend
unix 3 [ ] STREAM CONNECTED 359271 17737/mythbackend
unix 3 [ ] STREAM CONNECTED 359550 17737/mythbackend
unix 3 [ ] STREAM CONNECTED 359549 17737/mythbackend
unix 3 [ ] STREAM CONNECTED 359548 17737/mythbackend
unix 3 [ ] STREAM CONNECTED 359547 17737/mythbackend
unix 3 [ ] STREAM CONNECTED 359546 17737/mythbackend
unix 3 [ ] STREAM CONNECTED 359545 17737/mythbackend
unix 3 [ ] STREAM CONNECTED 359544 17737/mythbackend
unix 3 [ ] STREAM CONNECTED 359543 17737/mythbackend
unix 3 [ ] STREAM CONNECTED 359542 17737/mythbackend
unix 3 [ ] STREAM CONNECTED 359541 17737/mythbackend
unix 3 [ ] STREAM CONNECTED 359540 17737/mythbackend
unix 3 [ ] STREAM CONNECTED 359539 17737/mythbackend
unix 3 [ ] STREAM CONNECTED 359538 17737/mythbackend
unix 3 [ ] STREAM CONNECTED 359537 17737/mythbackend
unix 3 [ ] STREAM CONNECTED 359536 17737/mythbackend
unix 3 [ ] STREAM CONNECTED 359535 17737/mythbackend
richard@MythTV:~$
(I wasn't seeing the excessive cpu usage, since my MythTV system had recently been rebooted to install updates.)