Re: [Mplayerplug-in-devel] [mplayerplug-in-devel] Mplayerplug-in-rm crashes with .ram files
Brought to you by:
kdekorte
|
From: Kevin D. <kde...@gm...> - 2010-01-21 13:59:41
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 01/21/10 01:41, Barry Kauler wrote: > Hi, > I'm one of the developers of Puppy Linux. I'm working on a "next > generation" Puppy named "Quirky", using mplayer (compiled with > external ffmpeg) and mplayerplug-in. These are all the latest pulled > out of the respective version control systems, around January 16-17. > > I reported on building these packages in my blog: > http://bkhome.org/blog/?viewDetailed=01345 > > And released an experimental build (live-CD): > http://bkhome.org/blog/?viewDetailed=01348 > > ...the latter reports the problem of .ram files causing the browser to > crash. Further reports confirm this in the Puppy Linux forum. > > It's actually the plugin that crashes, taking SeaMonkey or Firefox with it. > > Here is an example URL: > > http://www.slp3d.com/ram/slp3d.ram > > The contents of this .ram file is this one line: > > rtsp://slp3d.rmod.llnwd.net/a1430/o16/show/webcast/real/slp3d.rm > > ...if I run mplayer directly with that URI, mplayer plays it. > > I looked in the mplayerplug-in mail archive and it seems this issue > came up back in 2007 and was resolved. Ah, but that was only for a > pnm:// protocol: > > http://sourceforge.net/mailarchive/message.php?msg_id=46C93E4F.2000708%40pienetworks.com > > ...that post described the essential problem as this: > > "Mplayerplug-in seems to be throwing the original .ram URL at mplayer, > which doesn't like it unless the -playlist option is set." > > Could one of you guys take a look at this for me? I've got this Quirky > Puppy live-CD at just 92.4MB that plays every media format we can > throw at it, absolutely beautiful, except for this one problem with > .ram files. > > Regards, > Barry Kauler Well pnm:// was added because rtsp:// was already there. Can you please provide a backtrace of the crash? Perhaps there is a pointer error somewhere. I'm guessing it might have something to do with the line just ending at the EOF, but unsure at this point as that site does not work for me. It just hangs during the connection stage. Kevin - -- Get my public GnuPG key from http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x7D0BD5D1 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iEYEARECAAYFAktYXcIACgkQ6w2kMH0L1dG0hgCcCiwie0Wqy8I8PKnyC8LUSGxO RXYAnRRXKSwz8tzrE6fSo2LTs21Jhgns =ZqZI -----END PGP SIGNATURE----- |