Newsticker
#1
Posted 16 June 2008 - 12:09
I have used the dreambox since a few hours now, and I see firefox using 80 to 90 CPU time. As there is no network activity, I suspect the "newsticker" to cause this phenomena. If I'm correct, does anyone have a hint how to get rid of this newsticker? I use Helenit final on a Dreambox 500+.
R.
Re: Newsticker #2
Posted 16 June 2008 - 12:21
http://downloads.pli.../all/ticker.php
Firefox under Linux btw ;-)
R.
Re: Newsticker #3
Posted 16 June 2008 - 12:35
You can temporary disable it in the webif menu itself. Somewhere right in the screen there's a menu to disable the newsticker (don't know the name as I don't have a dreambox here right now)
Re: Newsticker #4
Re: Newsticker #5
Posted 16 June 2008 - 12:43
I just did, and CPU usage is 0-1% (Firefox 2.0.0.14 on Windows XP). I can't detect any abnormal behaviour here...Put this in Firefox and you'll see all your cpu power consumed by this nonsense:
http://downloads.pli.../all/ticker.php
Firefox under Linux btw ;-)
Re: Newsticker #6
Re: Newsticker #7
Posted 16 June 2008 - 12:48
FF is notorious with regards to memory consumption, the longer you run, the more memory consumed, the slower it gets, and the more CPU it uses. This is especially noticeable when using Javascript (with the ticker does). In that case a restart of FF solves the problem (for a while). FF3 seems a lot better in that respect.
Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Pro (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)
Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.
Many answers to your question can be found in our new and improved wiki.
Re: Newsticker #8
Posted 16 June 2008 - 13:04
Re: Newsticker #9
Posted 16 June 2008 - 13:07
You might have an other problem.
FF is notorious with regards to memory consumption, the longer you run, the more memory consumed, the slower it gets, and the more CPU it uses. This is especially noticeable when using Javascript (with the ticker does). In that case a restart of FF solves the problem (for a while). FF3 seems a lot better in that respect.
I know. But that is not the problem. As soon as you load the ticker, it starts consuming CPU power. As soon as you stop the ticker, CPU consumption drops to normal proportions.
But there's someting else, maybe more severe: when choosing another (radio) station, the browser is getting the EPG a few times per second:
This is the dump of one of these connections:
Request:
GET /data HTTP/1.1
Host: dreambox1
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.14) Gecko/20080404 Iceweasel/2.0.0.14 (Debian-2.0.0.14-2)
Accept: text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 300
Connection: keep-alive
Referer: http://dreambox1/?screenWidth=1280
Cache-Control: max-age=0
Answer:
HTTP/1.1 200 OK
Connection: close
Content-Length: 1898
Content-Type: text/html; charset=utf-8
<html>
<head>
<script type="text/javascript">
function update()
{
if (parent.headerUpdateEPGData)
parent.headerUpdateEPGData(serviceName, nowT, nowD, nowSt, nextT, nextD, nextSt);
if (parent.headerUpdateStatusBar)
parent.headerUpdateStatusBar(vpid, apid, ip, lock, upTime, agc, snr, ber,satSyncStatus,satLockStatus);
if (parent.headerUpdateVolumeBar)
parent.headerUpdateVolumeBar(volume, mute);
if (parent.headerUpdateChannelStatusBar)
parent.headerUpdateChannelStatusBar(dolby, crypt, format);
if (parent.headerUpdateRecording)
parent.headerUpdateRecording(recording, recordChan);
if (parent.updateVideoBar)
parent.updateVideoBar(videoPosition, videoTime, diskGB, diskH);
}
</script>
</head>
<body onLoad="update()">
<script>
<!-- variables set by box -->
var updateCycleTime = 10000;
<!-- power state -->
var standby = 0;
<!-- service & epg data -->
var serviceName = "BBC R3";
var nowT = "13:00";
var nowD = "(60)";
var nowSt = "Composer of the Week";
var nextT = "";
var nextD = "";
var nextSt = "";
<!-- status bar -->
var diskGB = "n/a";
var diskH = "n/a";
var apid = "0x151b";
var vpid = "none";
var ip = "192.168.64.109";
var lock = "unlocked";
var upTime = "4:50 h up";
<!-- volume bar -->
var volume = 51;
var mute = 0;
<!-- channel stats -->
var dolby = 0;
var crypt = 0;
var format = 0;
<!-- recording -->
var recording = 0;
var recordChan = "";
<!-- vlc streaming -->
var vlcparms = "http://192.168.64.10...ffffffff,151b";
var serviceReference = "1:0:2:1a61:7dd:2:11a0000:0:0:0:";
var videoTime = "0:00";
var videoPosition = 0;
<!-- stream info -->
var agc = 74;
var snr = "87%";
var ber = 0;
var satSyncStatus = "on";
var satLockStatus = "on";
<!-- streaming client status -->
var streamingClientStatus = 2145118624;
</script>
</body>
</html>
Re: Newsticker #10
Posted 16 June 2008 - 13:11
Re: Newsticker #11
Posted 16 June 2008 - 13:18
Maybe this helps? Unfortunately I'm not a programmer so I won't be able to help.
Addition:
when clicking the "Radio" button on the left, the refresh time increases from a few times per second to something like once per 10 seconds.
Re: Newsticker #12
Re: Newsticker #13
Posted 16 June 2008 - 15:52
Btw: putting the ticker URL to the blacklist of the proxy "resolves" the ticker problem for me at the moment
Re: Newsticker #14
Posted 16 June 2008 - 16:05
data: var vlcparms = "http://192.168.64.109:31339/0,0105,ffffffff,151b"; zap.js: function vlcStart() { if (parent.data.vlcparms) { if (parent.data.vlcparms.indexOf("ffffffff") == -1) { ... } else { parent.data.location.reload(); ... } } ... }
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users