Thread: [Mplayerplug-in-devel] [mplayerplug-in-devel] Mplayerplug-in-rm crashes with .ram files
Brought to you by:
kdekorte
Menu
▾
▴
mplayerplug-in-devel
|
From: Barry K. <bk...@gm...> - 2010-01-21 08:41:17
|
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 |
|
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----- |
|
From: Barry K. <bk...@gm...> - 2010-01-23 11:34:29
|
Kevin wrote: "I'm guessing it might have something to do with the line just ending at the EOF" Yes, that's it! I downloaded that .ram file from: http://www.slp3d.com/ram/slp3d.ram If I open it using File -> Open, the browser crashes. However, after editing the file and putting a carriage-return on the end, it works! I'm extremely mediocre at C coding... would it be pretty simple to test for that condition and either insert a carriage-return or code a workaround? Regards, Barry Kauler On 1/21/10, Kevin DeKorte <kde...@gm...> wrote: > -----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----- > > ------------------------------------------------------------------------------ > Throughout its 18-year history, RSA Conference consistently attracts the > world's best and brightest in the field, creating opportunities for > Conference > attendees to learn about information security's most important issues > through > interactions with peers, luminaries and emerging and established companies. > http://p.sf.net/sfu/rsaconf-dev2dev > _______________________________________________ > Mplayerplug-in-devel mailing list > Mpl...@li... > https://lists.sourceforge.net/lists/listinfo/mplayerplug-in-devel > |
|
From: Kevin D. <kde...@gm...> - 2010-01-23 14:35:39
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 01/23/2010 04:28 AM, Barry Kauler wrote: > Kevin wrote: > > "I'm guessing it might have something to do with the line just ending at > the EOF" > > Yes, that's it! > > I downloaded that .ram file from: > > http://www.slp3d.com/ram/slp3d.ram > > If I open it using File -> Open, the browser crashes. However, after > editing the file and putting a carriage-return on the end, it works! > > I'm extremely mediocre at C coding... would it be pretty simple to > test for that condition and either insert a carriage-return or code a > workaround? > > Regards, > Barry Kauler Barry, I still need the backtrace, because I am testing for EOF already. 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/ iEYEARECAAYFAktbCTAACgkQ6w2kMH0L1dEiGQCeJ/b6i3PsM/KMutpj12zCyOr9 xl4AoIziDxfiuSf1PcQUGTZ2cKuAiARE =yAu0 -----END PGP SIGNATURE----- |
|
From: Barry K. <bk...@gm...> - 2010-01-24 11:46:44
Attachments:
plugin-list.cpp.gz
|
> "I'm guessing it might have something to do with the line just ending at > the EOF" > > Yes, that's it! I have fixed it, at least for my example .ram file. Patched file 'plugin-list.cpp' attached. The problem was that the test for EOF was not working, and the while-loop that it is in gets re-entered, then everything is messed up and it crashes. Regards, Barry Kauler On 1/23/10, Kevin DeKorte <kde...@gm...> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 01/23/2010 04:28 AM, Barry Kauler wrote: >> Kevin wrote: >> >> "I'm guessing it might have something to do with the line just ending at >> the EOF" >> >> Yes, that's it! >> >> I downloaded that .ram file from: >> >> http://www.slp3d.com/ram/slp3d.ram >> >> If I open it using File -> Open, the browser crashes. However, after >> editing the file and putting a carriage-return on the end, it works! >> >> I'm extremely mediocre at C coding... would it be pretty simple to >> test for that condition and either insert a carriage-return or code a >> workaround? >> >> Regards, >> Barry Kauler > > Barry, > > I still need the backtrace, because I am testing for EOF already. > > 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/ > > iEYEARECAAYFAktbCTAACgkQ6w2kMH0L1dEiGQCeJ/b6i3PsM/KMutpj12zCyOr9 > xl4AoIziDxfiuSf1PcQUGTZ2cKuAiARE > =yAu0 > -----END PGP SIGNATURE----- > > ------------------------------------------------------------------------------ > Throughout its 18-year history, RSA Conference consistently attracts the > world's best and brightest in the field, creating opportunities for > Conference > attendees to learn about information security's most important issues > through > interactions with peers, luminaries and emerging and established companies. > http://p.sf.net/sfu/rsaconf-dev2dev > _______________________________________________ > Mplayerplug-in-devel mailing list > Mpl...@li... > https://lists.sourceforge.net/lists/listinfo/mplayerplug-in-devel > |
|
From: Kevin D. <kde...@gm...> - 2010-01-24 15:23:50
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 01/24/10 04:46, Barry Kauler wrote: >> "I'm guessing it might have something to do with the line just ending at >> the EOF" >> >> Yes, that's it! > > I have fixed it, at least for my example .ram file. > > Patched file 'plugin-list.cpp' attached. > > The problem was that the test for EOF was not working, and the > while-loop that it is in gets re-entered, then everything is messed up > and it crashes. > > Regards, > Barry Kauler Ok, I looked at the code you submitted and based on that fixed up the code in CVS. So can you try that code and see if it works correctly. 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/ iEYEARECAAYFAktcZe4ACgkQ6w2kMH0L1dHvhACfetSrATbF8LQCdm1sbKAtyjPJ YlcAn3xyq9FkXrMbmxXNL8RLC8VVrcXC =KVlo -----END PGP SIGNATURE----- |
Thanks for helping keep SourceForge clean.
X