It's me again.
Today both my friend (Simon) and I have tested on two similar Dell GX270
machines (Pentium 4 1 Gb of ram if I'm correct). Mine having Debian
Sarge running them player-586 1:1.0-pre6cvs20050409-0sarge0.1 and my
friends computer using Fedora Core 4 test 2 and prepackaged rpm of
I'm now describing my tests:
When I run firefox with the default cachesize no of the DR stations
work (I tested both the DR netplayer and the direct links).
When I set any other values than 0 (zero) still nothing happens. (I've
tried 16, 8, 4, 3 and 1)
When I set cachesize to 0 (zero) every channel works both in the DR
netplayer (P1, P2, P3 and the other channel possibilities in
http://www.dr.dk/ in the top of the page 'H=D8R RADIO' and 'V=E6lg kanal'
push down menu) as well as the direct links meaning both the 'xxKbps'
and the 'direkte' links from the
When the cachesize is minimized to 0 (zero) a movieclip I tested did not
work anymore but that seems to be obvious that this will happen. (I
tested http://www.dr.dk/konsum/asx/2005/uds2_05/uds2.asx with the
cachesize of 256 it worked with e.g. 16 or 0 (zero) it didn't but that
is of course obvious.)
My intuition tells me that the parsing of the options in e.g.
mplayerplug-in.conf might share some memory which should not be shared
when the options are deciphered (well what do I know). So all the
possible options that you have in the plugin process might get obscured
because of this.
But still suddenly firefox crashes with a segmentation fault (and that
even when I set the option cachesize down to 0 (zero).
Another problem is that sometimes shifting channels causes another instan=
ce of mplayer to occur without the previous instance shutting down, at th=
e end leaving several mplayer instances running. I've had as many as five=
mplayers running at the same time, and at some point sound can no longer=
be heard. Killing some of the mplayer instances can suddenly bring back =
I have so far only seen it crash and/or freeze when I shifted channel.
Maybe when it freezes(!) it is because the plugin can not kill the
earlier mplayer process. I see this in the output (of the debug
information) that mplayerplug-in tries to kill mplayer and when I close
firefox one or two instances of mplayer still exists.
But remember that crashes sometimes occur when I shift channel and the
firefox windows just close instantly.
My friend has had exact similar observations on his Fedora Core 4 test
2 also the issue about that firefox sometimes suddenly crashes and
closes its window, and that several mplayer instances exists when shiftin=