Thread: Re: [Mplayerplug-in-devel] Mplayer Stops
Brought to you by:
kdekorte
From: raid517 <ra...@uk...> - 2005-10-19 09:52:16
|
mplayer is found in the path, so having a hard coded path would not give any advantage. That is why I asked you what the output of 'which mplayer' was, it was to ensure it was in the path and could be found. Any luck with the commandline I sent you to try? Kevin Hi Kevin, thanks for your help in this matter. I can tell you that the command (minus the extra -) works - but that the video plays very slowly. I'm not sure if it is network traffic on sourceforge (it's not at my end as i have an 8Mbs connection) so i will try again a little later and let you know. Best regards, GJ |
From: raid517 <ra...@uk...> - 2005-10-21 22:33:33
|
Kevin I tried the newest CVS code as of 11:30pm London time. I'm assuming that your fixes haven't been commited yet as I am still having the same problem. I am sure it has something to do with the way the HD movie buttons are displayed on the Apple web site, because if I navagate away from that particular web page when a movie finishes playing, I can avoid a crash. I am not sure if this counts as useful information or not. I will try CVS again tomorrow. :) GJ |
From: Kevin D. <kde...@ya...> - 2005-10-21 23:04:13
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 You'll know you have the change when the ChangeLog file has the following lines at the top Make onMouseDown and onMouseUp actually work Adding some locks back in and disable killmplayer function (causes a long wait) Fixed crash when you have two players on a page and browser window closed SourceForge takes awhile to update it's anonymous CVS. But I have checked it and it should be there. I did the following test and it didn't crash for me Open a browser and then open another browser window. In the second window open the HD Harry Potter site (get 6 buttons) I click the 480p button and wait for it to show the "Green Preview Screen" and then close the second browser window and it closed correctly and the first window remained running. It had something to do with two plugins being loaded, because if I do it with only one plugin it does not crash. Which is interesting in itself, because the plugins should be isolated from each other. Except for global variables of which I have two errno (libc standard) and DEBUG which is mainly a readonly variable and if it is modified nothing cares. Prior to the patch, this test did not succeed for me. Kevin raid517 wrote: > Kevin I tried the newest CVS code as of 11:30pm London time. I'm > assuming that your fixes haven't been commited yet as I am still having > the same problem. I am sure it has something to do with the way the HD > movie buttons are displayed on the Apple web site, because if I navagate > away from that particular web page when a movie finishes playing, I can > avoid a crash. > > I am not sure if this counts as useful information or not. > > I will try CVS again tomorrow. :) > > GJ > > > ------------------------------------------------------- > This SF.Net email is sponsored by: > Power Architecture Resource Center: Free content, downloads, discussions, > and more. http://solutions.newsforge.com/ibmarch.tmpl > _______________________________________________ > Mplayerplug-in-devel mailing list > Mpl...@li... > https://lists.sourceforge.net/lists/listinfo/mplayerplug-in-devel > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDWXPdaR60qN0tF+8RAmJbAJ9boarL00RAxJvWlpoaYAd4VDjlTQCgzVL0 aEhaGUZD0WJ0GaIPIsDs6qs= =Agea -----END PGP SIGNATURE----- |
From: raid517 <ra...@uk...> - 2005-10-21 23:52:46
|
Well that is depressing Kevin, because I actually have the latest CVS - and I am still having problems. If it helps, the conditions you described are somewhat different to what i described. A more detailed example might suffice: I am not a huge fan of tabbed browsing (yes I know it is against the grain - but there you are as a linux user for the last 4 years I still (as I supect do many people) default to the old IE behaviour of opening new Windows when I want to keep a particular page open - but I also want to navagate to another site). To this end to test this: Open 3 random new Firefox instances (as in don't use tabs). Use one of these Firefox browser windows to navagate to the Apple site. Play some HD content. (any resolution is fine). Let it play to the end. Close the Mplayer Plugin Window Now also close the Apple web page that you launched Mplayer plugin from to watch your movie trailer. The result of this for me, is that the remaining two open windows crash with a segefault. (The same one that I gave you in the firefox debug I sent a few emails ago). Unfortunately the new code is also it seems occasionally causing Firefox to hang on launch. The only way to overcome this is if I kill all running firefox processes and then attempt to run it again. Uninstalling the plugins overcomes this problem. I'm sorry to be a pain. I know you thought you had nailed it... GJ Kevin DeKorte wrote: >-----BEGIN PGP SIGNED MESSAGE----- >Hash: SHA1 > >You'll know you have the change when the ChangeLog file has the >following lines at the top > > Make onMouseDown and onMouseUp actually work > Adding some locks back in and disable killmplayer function (causes a >long wait) > Fixed crash when you have two players on a page and browser window closed > >SourceForge takes awhile to update it's anonymous CVS. But I have >checked it and it should be there. > >I did the following test and it didn't crash for me > >Open a browser and then open another browser window. In the second >window open the HD Harry Potter site (get 6 buttons) I click the 480p >button and wait for it to show the "Green Preview Screen" and then close >the second browser window and it closed correctly and the first window >remained running. It had something to do with two plugins being loaded, >because if I do it with only one plugin it does not crash. Which is >interesting in itself, because the plugins should be isolated from each >other. Except for global variables of which I have two errno (libc >standard) and DEBUG which is mainly a readonly variable and if it is >modified nothing cares. > >Prior to the patch, this test did not succeed for me. > >Kevin > > >raid517 wrote: > > >>Kevin I tried the newest CVS code as of 11:30pm London time. I'm >>assuming that your fixes haven't been commited yet as I am still having >>the same problem. I am sure it has something to do with the way the HD >>movie buttons are displayed on the Apple web site, because if I navagate >>away from that particular web page when a movie finishes playing, I can >>avoid a crash. >> >>I am not sure if this counts as useful information or not. >> >>I will try CVS again tomorrow. :) >> >>GJ >> >> >>------------------------------------------------------- >>This SF.Net email is sponsored by: >>Power Architecture Resource Center: Free content, downloads, discussions, >>and more. http://solutions.newsforge.com/ibmarch.tmpl >>_______________________________________________ >>Mplayerplug-in-devel mailing list >>Mpl...@li... >>https://lists.sourceforge.net/lists/listinfo/mplayerplug-in-devel >> >> >> > >-----BEGIN PGP SIGNATURE----- >Version: GnuPG v1.4.1 (GNU/Linux) > >iD8DBQFDWXPdaR60qN0tF+8RAmJbAJ9boarL00RAxJvWlpoaYAd4VDjlTQCgzVL0 >aEhaGUZD0WJ0GaIPIsDs6qs= >=Agea >-----END PGP SIGNATURE----- > > >------------------------------------------------------- >This SF.Net email is sponsored by: >Power Architecture Resource Center: Free content, downloads, discussions, >and more. http://solutions.newsforge.com/ibmarch.tmpl >_______________________________________________ >Mplayerplug-in-devel mailing list >Mpl...@li... >https://lists.sourceforge.net/lists/listinfo/mplayerplug-in-devel > > > > |
From: Kevin D. <kde...@ya...> - 2005-10-22 00:14:33
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Well, I tried it we 3 different trailers in the setup you described and I can't get it to crash for me. And I don't experience the lag on loading. Kevin raid517 wrote: > Well that is depressing Kevin, because I actually have the latest CVS - > and I am still having problems. If it helps, the conditions you > described are somewhat different to what i described. > > A more detailed example might suffice: > > I am not a huge fan of tabbed browsing (yes I know it is against the > grain - but there you are as a linux user for the last 4 years I still > (as I supect do many people) default to the old IE behaviour of opening > new Windows when I want to keep a particular page open - but I also want > to navagate to another site). > > To this end to test this: > > Open 3 random new Firefox instances (as in don't use tabs). > > Use one of these Firefox browser windows to navagate to the Apple site. > > Play some HD content. (any resolution is fine). > > Let it play to the end. > > Close the Mplayer Plugin Window > > Now also close the Apple web page that you launched Mplayer plugin from > to watch your movie trailer. > > The result of this for me, is that the remaining two open windows crash > with a segefault. (The same one that I gave you in the firefox debug I > sent a few emails ago). > > Unfortunately the new code is also it seems occasionally causing Firefox > to hang on launch. The only way to overcome this is if I kill all > running firefox processes and then attempt to run it again. Uninstalling > the plugins overcomes this problem. > > I'm sorry to be a pain. I know you thought you had nailed it... > > GJ > > > Kevin DeKorte wrote: > > You'll know you have the change when the ChangeLog file has the > following lines at the top > > Make onMouseDown and onMouseUp actually work > Adding some locks back in and disable killmplayer function (causes a > long wait) > Fixed crash when you have two players on a page and browser window > closed > > SourceForge takes awhile to update it's anonymous CVS. But I have > checked it and it should be there. > > I did the following test and it didn't crash for me > > Open a browser and then open another browser window. In the second > window open the HD Harry Potter site (get 6 buttons) I click the 480p > button and wait for it to show the "Green Preview Screen" and then close > the second browser window and it closed correctly and the first window > remained running. It had something to do with two plugins being loaded, > because if I do it with only one plugin it does not crash. Which is > interesting in itself, because the plugins should be isolated from each > other. Except for global variables of which I have two errno (libc > standard) and DEBUG which is mainly a readonly variable and if it is > modified nothing cares. > > Prior to the patch, this test did not succeed for me. > > Kevin > > > raid517 wrote: > > >>>> Kevin I tried the newest CVS code as of 11:30pm London time. I'm >>>> assuming that your fixes haven't been commited yet as I am still having >>>> the same problem. I am sure it has something to do with the way the HD >>>> movie buttons are displayed on the Apple web site, because if I navagate >>>> away from that particular web page when a movie finishes playing, I can >>>> avoid a crash. >>>> >>>> I am not sure if this counts as useful information or not. >>>> >>>> I will try CVS again tomorrow. :) >>>> >>>> GJ >>>> >>>> >>>> ------------------------------------------------------- >>>> This SF.Net email is sponsored by: >>>> Power Architecture Resource Center: Free content, downloads, >>>> discussions, >>>> and more. http://solutions.newsforge.com/ibmarch.tmpl >>>> _______________________________________________ >>>> Mplayerplug-in-devel mailing list >>>> Mpl...@li... >>>> https://lists.sourceforge.net/lists/listinfo/mplayerplug-in-devel >>>> >>>> > > >> >> - ------------------------------------------------------- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl _______________________________________________ Mplayerplug-in-devel mailing list Mpl...@li... https://lists.sourceforge.net/lists/listinfo/mplayerplug-in-devel >> >> >> -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDWYRcaR60qN0tF+8RAni4AJ0UW4t/Qxpn+mdmRLddZE9mDcBdrwCglsRU VlYOYawFHhvuBAHJozM/p/8= =NuMV -----END PGP SIGNATURE----- |
From: raid517 <ra...@uk...> - 2005-10-22 01:52:47
Attachments:
Firefox_Crash
|
Good news Kevin, it appears you are in the clear. I had a hunch and decided to not use Mplayer plugin and just try some rapid browsing of the Apple site to see if I could make Firefox crash under normal conditions. I quickly found that if I rapidly flipped back and forth between the Apple movie trailer site and the Quicktime download page (with only a single window open) withou waiting for either to fully load I could make it crash fairly reliably. So I ran firefox from the command line and repeated the exercise. When the browser crashed it filled my console with a zillion error messages (see attachment if curious) - which i think may be associated with a fault in some graphics library or other that Firefox may be using. (Just a wild guess though ATM). Well anyway this inspired me to try Mozilla Browser in place of Firefox - and I am pleased to say that this does seem somewhat more stable. (Not 100% because I can still make it crash, it just take a bit more effort to do). So the bottom line is that the fault appears to be with the software on my system - and not with your coding. :) It's a lot to ask I guess, but I don't suppose you can make any sense of all of the junk messages that Firefox spits out before it dies? It would just be helpful to know so that maybe I could pin my finger on something definate for when I submit a bug to the Firefox devs. (Although given the amount of time it can take for Firefox devs to fix problems, I am not optomistic for a quick fix. Still if I report it as part of the beta (since the latest beta also crashes) then who knows?). It is odd that you were (at one point) able to repeat this behaviour too. It may just be a little more random and infrequent for you, so that maybe your code was never really at fault to begin with? GJ Kevin DeKorte wrote: >-----BEGIN PGP SIGNED MESSAGE----- >Hash: SHA1 > >Well, I tried it we 3 different trailers in the setup you described and >I can't get it to crash for me. And I don't experience the lag on loading. > >Kevin > > >raid517 wrote: > > >>Well that is depressing Kevin, because I actually have the latest CVS - >>and I am still having problems. If it helps, the conditions you >>described are somewhat different to what i described. >> >>A more detailed example might suffice: >> >>I am not a huge fan of tabbed browsing (yes I know it is against the >>grain - but there you are as a linux user for the last 4 years I still >>(as I supect do many people) default to the old IE behaviour of opening >>new Windows when I want to keep a particular page open - but I also want >>to navagate to another site). >> >>To this end to test this: >> >>Open 3 random new Firefox instances (as in don't use tabs). >> >>Use one of these Firefox browser windows to navagate to the Apple site. >> >>Play some HD content. (any resolution is fine). >> >>Let it play to the end. >> >>Close the Mplayer Plugin Window >> >>Now also close the Apple web page that you launched Mplayer plugin from >>to watch your movie trailer. >> >>The result of this for me, is that the remaining two open windows crash >>with a segefault. (The same one that I gave you in the firefox debug I >>sent a few emails ago). >> >>Unfortunately the new code is also it seems occasionally causing Firefox >>to hang on launch. The only way to overcome this is if I kill all >>running firefox processes and then attempt to run it again. Uninstalling >>the plugins overcomes this problem. >> >>I'm sorry to be a pain. I know you thought you had nailed it... >> >>GJ >> >> >>Kevin DeKorte wrote: >> >>You'll know you have the change when the ChangeLog file has the >>following lines at the top >> >> Make onMouseDown and onMouseUp actually work >> Adding some locks back in and disable killmplayer function (causes a >>long wait) >> Fixed crash when you have two players on a page and browser window >>closed >> >>SourceForge takes awhile to update it's anonymous CVS. But I have >>checked it and it should be there. >> >>I did the following test and it didn't crash for me >> >>Open a browser and then open another browser window. In the second >>window open the HD Harry Potter site (get 6 buttons) I click the 480p >>button and wait for it to show the "Green Preview Screen" and then close >>the second browser window and it closed correctly and the first window >>remained running. It had something to do with two plugins being loaded, >>because if I do it with only one plugin it does not crash. Which is >>interesting in itself, because the plugins should be isolated from each >>other. Except for global variables of which I have two errno (libc >>standard) and DEBUG which is mainly a readonly variable and if it is >>modified nothing cares. >> >>Prior to the patch, this test did not succeed for me. >> >>Kevin >> >> >>raid517 wrote: >> >> >> >> >>>>>Kevin I tried the newest CVS code as of 11:30pm London time. I'm >>>>>assuming that your fixes haven't been commited yet as I am still having >>>>>the same problem. I am sure it has something to do with the way the HD >>>>>movie buttons are displayed on the Apple web site, because if I navagate >>>>>away from that particular web page when a movie finishes playing, I can >>>>>avoid a crash. >>>>> >>>>>I am not sure if this counts as useful information or not. >>>>> >>>>>I will try CVS again tomorrow. :) >>>>> >>>>>GJ >>>>> >>>>> >>>>>------------------------------------------------------- >>>>>This SF.Net email is sponsored by: >>>>>Power Architecture Resource Center: Free content, downloads, >>>>>discussions, >>>>>and more. http://solutions.newsforge.com/ibmarch.tmpl >>>>>_______________________________________________ >>>>>Mplayerplug-in-devel mailing list >>>>>Mpl...@li... >>>>>https://lists.sourceforge.net/lists/listinfo/mplayerplug-in-devel >>>>> >>>>> >>>>> >>>>> >> >> >>> >>> >- ------------------------------------------------------- >This SF.Net email is sponsored by: >Power Architecture Resource Center: Free content, downloads, discussions, >and more. http://solutions.newsforge.com/ibmarch.tmpl >_______________________________________________ >Mplayerplug-in-devel mailing list >Mpl...@li... >https://lists.sourceforge.net/lists/listinfo/mplayerplug-in-devel > > >>> >>> > > > > > > >-----BEGIN PGP SIGNATURE----- >Version: GnuPG v1.4.1 (GNU/Linux) > >iD8DBQFDWYRcaR60qN0tF+8RAni4AJ0UW4t/Qxpn+mdmRLddZE9mDcBdrwCglsRU >VlYOYawFHhvuBAHJozM/p/8= >=NuMV >-----END PGP SIGNATURE----- > > >------------------------------------------------------- >This SF.Net email is sponsored by: >Power Architecture Resource Center: Free content, downloads, discussions, >and more. http://solutions.newsforge.com/ibmarch.tmpl >_______________________________________________ >Mplayerplug-in-devel mailing list >Mpl...@li... >https://lists.sourceforge.net/lists/listinfo/mplayerplug-in-devel > > > > |
From: Kevin D. <kde...@ya...> - 2005-10-22 03:57:48
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Thanks for the kind words about my coding, but as anyone who has been around this project will know is that I have struggled with crashes in mplayerplug-in for a long time. I believe that we did have a real error earlier and that finding and fixing the crash is a positive thing. So your problem did help make the product better. The project went thru a rather painful process betweed 2.95 and 3.05. Hours were spent debugging some odd crashes. Eventually I and several other people came up with some test cases and solutions to these crashes. So reports of crashes always have a high priority especially since we had recently reached a stable codebase. The errors from firefox look like errors I see when I run with KDE as my desktop and use the gtk-qt-engine which maps GTK widgets to QT (KDE) widgets. Or they could just be poor/unfinished cleanup. Kevin raid517 wrote: > Good news Kevin, it appears you are in the clear. > > I had a hunch and decided to not use Mplayer plugin and just try some > rapid browsing of the Apple site to see if I could make Firefox crash > under normal conditions. > > I quickly found that if I rapidly flipped back and forth between the > Apple movie trailer site and the Quicktime download page (with only a > single window open) withou waiting for either to fully load I could make > it crash fairly reliably. > > So I ran firefox from the command line and repeated the exercise. > > When the browser crashed it filled my console with a zillion error > messages (see attachment if curious) - which i think may be associated > with a fault in some graphics library or other that Firefox may be > using. (Just a wild guess though ATM). > > Well anyway this inspired me to try Mozilla Browser in place of Firefox > - and I am pleased to say that this does seem somewhat more stable. > (Not 100% because I can still make it crash, it just take a bit more > effort to do). > > So the bottom line is that the fault appears to be with the software on > my system - and not with your coding. :) > > It's a lot to ask I guess, but I don't suppose you can make any sense of > all of the junk messages that Firefox spits out before it dies? It would > just be helpful to know so that maybe I could pin my finger on something > definate for when I submit a bug to the Firefox devs. (Although given > the amount of time it can take for Firefox devs to fix problems, I am > not optomistic for a quick fix. Still if I report it as part of the beta > (since the latest beta also crashes) then who knows?). > > It is odd that you were (at one point) able to repeat this behaviour > too. It may just be a little more random and infrequent for you, so that > maybe your code was never really at fault to begin with? > > > GJ > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDWbizaR60qN0tF+8RAhUvAJ4nd63ZUYFHOOb/i67lAi6NpUMbyQCeL/nd l/HnMOXU9yJELIH/EH+htBI= =aiwB -----END PGP SIGNATURE----- |
From: Kevin D. <kde...@ya...> - 2005-10-22 12:49:36
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Nope that is not it. I just tested with KDE on my machine using the gtk-qt-engine and using the clearlooks and I could not get it to crash in either case in KDE. Perhaps you can try disabling the gtk-qt-engine for some tests. You also might want to make sure that engine is up to date. I think the gtk-qt-engine project might be abandoned as there have not been many updates to it in several months. I find it very interesting that it does not crash outside of KDE. Up until about a month ago I was a KDE user and developed mplayerplug-in using KDE as my normal desktop. So if there was a compatibility issue, I probably would have seen it. I switched to GNOME when I upgraded from FC3 to FC4 just to try it out. I might go back, but so far pretty much everything I want it working. Kevin raid517 wrote: > Hi Kevin, good news and bad I'm afraid. You seem to have hit the nail on > the head. There doesn't seem to be any problem with Firefox after all. > It appears to be a conflict between Mplayer Plugin and the GTK graphics > library you mentioned. (Or at least it is certainly something in KDE). > Since this is Linux thankfully we have several choices, so I opted to > rerun the tests in both IceWM and fluxbox. > > I am pleased to report that all tests passed cleanly with no crashes. > > Logging back into KDE however, brought the problem back again. > > This is a little unfortunate as I freely admit I am a hard core KDE fan > (with a smaller soft spot for Fluxbox) and have just spent the last > several days building a new computer and installing and configuring > (including theming) the perfect KDE system as a birthday gift for a > young friend of mine. (I figured that if I take out all the hard work of > setting up a Linux system for them, that they should really get along > pretty well with it). > > Well anyway the point is I very much like KDE and I would like to > continue using it - and i like the GTK theming support too as it lends > consitancy to all of the apps on my desktop (I assume though that we are > talking about the same thing here?). > > So I guess the question is, is there any possibility that you might be > able to fix what does now after all appear to be a genuine bug? > > I think that is where the problem may have been... We were speaking two > different languages. While I was talking KDE, you were talking fluxbox, > or Gnome - or whatever other desktop you may currently be using. > > But it does now seem that the problem is isolated to an incompatability > with KDE and Mplayer plugin. > > I hope this helps. > > GJ > > > > Kevin DeKorte wrote: > > Thanks for the kind words about my coding, but as anyone who has been > around this project will know is that I have struggled with crashes in > mplayerplug-in for a long time. I believe that we did have a real error > earlier and that finding and fixing the crash is a positive thing. So > your problem did help make the product better. The project went thru a > rather painful process betweed 2.95 and 3.05. Hours were spent debugging > some odd crashes. Eventually I and several other people came up with > some test cases and solutions to these crashes. So reports of crashes > always have a high priority especially since we had recently reached a > stable codebase. > > The errors from firefox look like errors I see when I run with KDE as my > desktop and use the gtk-qt-engine which maps GTK widgets to QT (KDE) > widgets. Or they could just be poor/unfinished cleanup. > > Kevin > > raid517 wrote: > > >>>> Good news Kevin, it appears you are in the clear. >>>> >>>> I had a hunch and decided to not use Mplayer plugin and just try some >>>> rapid browsing of the Apple site to see if I could make Firefox crash >>>> under normal conditions. >>>> >>>> I quickly found that if I rapidly flipped back and forth between the >>>> Apple movie trailer site and the Quicktime download page (with only a >>>> single window open) withou waiting for either to fully load I could make >>>> it crash fairly reliably. >>>> >>>> So I ran firefox from the command line and repeated the exercise. >>>> >>>> When the browser crashed it filled my console with a zillion error >>>> messages (see attachment if curious) - which i think may be associated >>>> with a fault in some graphics library or other that Firefox may be >>>> using. (Just a wild guess though ATM). >>>> >>>> Well anyway this inspired me to try Mozilla Browser in place of Firefox >>>> - and I am pleased to say that this does seem somewhat more stable. >>>> (Not 100% because I can still make it crash, it just take a bit more >>>> effort to do). >>>> >>>> So the bottom line is that the fault appears to be with the software on >>>> my system - and not with your coding. :) >>>> >>>> It's a lot to ask I guess, but I don't suppose you can make any sense of >>>> all of the junk messages that Firefox spits out before it dies? It would >>>> just be helpful to know so that maybe I could pin my finger on something >>>> definate for when I submit a bug to the Firefox devs. (Although given >>>> the amount of time it can take for Firefox devs to fix problems, I am >>>> not optomistic for a quick fix. Still if I report it as part of the beta >>>> (since the latest beta also crashes) then who knows?). >>>> >>>> It is odd that you were (at one point) able to repeat this behaviour >>>> too. It may just be a little more random and infrequent for you, so that >>>> maybe your code was never really at fault to begin with? >>>> >>>> >>>> GJ >>>> >>>> > >> >> - ------------------------------------------------------- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl _______________________________________________ Mplayerplug-in-devel mailing list Mpl...@li... https://lists.sourceforge.net/lists/listinfo/mplayerplug-in-devel >> >> >> -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDWjVOaR60qN0tF+8RAgi3AJ9hvMJH8lFtmzxx608ObKnZ0oEVAgCfTVrP rqhu6PFYCn4spym7mpxAHvw= =6akw -----END PGP SIGNATURE----- |
From: raid517 <ra...@uk...> - 2005-10-22 13:33:30
|
You beat me to it Kevin, I was just going to write you a short note. In any case I disabled GTK theming support in KDE and I can report that there are no more crashes. (I am of course talking about the look and feel section of KDE control -> use KDE themes and fonts in GTK apps). Of course this does have the unfortunate effect that several of my apps don't look as consistant as they once did, but there we have it.... There isn't much I can do about that I imagine, especially if as you say the GTK theming project is no longer being maintained. It was actually you who pointed me to this (although I had something of a hunch) so I am certainly grateful to you for that. (Nonetheless if there was ever a better resolution I would certainly welcome it). As for the KDE v's Gnome thing, I don't think I could ever switch. After 4 years of KDE I have become a little set in my ways I think. There a lot's of KDE specific little convieniences that are simply missing from Gnome (although I hear Ubuntu does a very good Gnome) and I don't really have the patience to relearn how to do things that right now really come already quite naturally to me. But anyway I digress. The results of my tests are as follows: No Mplayer Plugin Crashes in Fluxbox, Ice WM or XFCE. No Mplayer Plugin Crashes in KDE with GTK theming support disabled. Frequent and regular crashes with Mplayer plugin installed and GTK theming support enabled. No crashes with GTK theming support enabled and Mplayer plugin uninstalled. I don't know if this is meaningful to you, but this is what has turned out to be true in my specific case. I don't know if you can read too much into the 'works for me' type scenario that you described either though - as having had a great deal of experience with computers, it seems to me that almost every computer I have ever encountered is as different from every other computer, as every person I have ever met is as unique and different from each other too. There are just too many configurations to always accurately predict what will happen in a specific instance on a specific platform. In any case I hope the information I have supplied is of use to you - and to the Mplayer plugin user base. Best regards, GJ Kevin DeKorte wrote: >-----BEGIN PGP SIGNED MESSAGE----- >Hash: SHA1 > >Nope that is not it. I just tested with KDE on my machine using the >gtk-qt-engine and using the clearlooks and I could not get it to crash >in either case in KDE. Perhaps you can try disabling the gtk-qt-engine >for some tests. You also might want to make sure that engine is up to >date. I think the gtk-qt-engine project might be abandoned as there have >not been many updates to it in several months. > >I find it very interesting that it does not crash outside of KDE. Up >until about a month ago I was a KDE user and developed mplayerplug-in >using KDE as my normal desktop. So if there was a compatibility issue, I >probably would have seen it. I switched to GNOME when I upgraded from >FC3 to FC4 just to try it out. I might go back, but so far pretty much >everything I want it working. > >Kevin > >raid517 wrote: > > >>Hi Kevin, good news and bad I'm afraid. You seem to have hit the nail on >>the head. There doesn't seem to be any problem with Firefox after all. >>It appears to be a conflict between Mplayer Plugin and the GTK graphics >>library you mentioned. (Or at least it is certainly something in KDE). >>Since this is Linux thankfully we have several choices, so I opted to >>rerun the tests in both IceWM and fluxbox. >> >>I am pleased to report that all tests passed cleanly with no crashes. >> >>Logging back into KDE however, brought the problem back again. >> >>This is a little unfortunate as I freely admit I am a hard core KDE fan >>(with a smaller soft spot for Fluxbox) and have just spent the last >>several days building a new computer and installing and configuring >>(including theming) the perfect KDE system as a birthday gift for a >>young friend of mine. (I figured that if I take out all the hard work of >>setting up a Linux system for them, that they should really get along >>pretty well with it). >> >>Well anyway the point is I very much like KDE and I would like to >>continue using it - and i like the GTK theming support too as it lends >>consitancy to all of the apps on my desktop (I assume though that we are >>talking about the same thing here?). >> >>So I guess the question is, is there any possibility that you might be >>able to fix what does now after all appear to be a genuine bug? >> >>I think that is where the problem may have been... We were speaking two >>different languages. While I was talking KDE, you were talking fluxbox, >>or Gnome - or whatever other desktop you may currently be using. >> >>But it does now seem that the problem is isolated to an incompatability >>with KDE and Mplayer plugin. >> >>I hope this helps. >> >>GJ >> >> >> >>Kevin DeKorte wrote: >> >>Thanks for the kind words about my coding, but as anyone who has been >>around this project will know is that I have struggled with crashes in >>mplayerplug-in for a long time. I believe that we did have a real error >>earlier and that finding and fixing the crash is a positive thing. So >>your problem did help make the product better. The project went thru a >>rather painful process betweed 2.95 and 3.05. Hours were spent debugging >>some odd crashes. Eventually I and several other people came up with >>some test cases and solutions to these crashes. So reports of crashes >>always have a high priority especially since we had recently reached a >>stable codebase. >> >>The errors from firefox look like errors I see when I run with KDE as my >>desktop and use the gtk-qt-engine which maps GTK widgets to QT (KDE) >>widgets. Or they could just be poor/unfinished cleanup. >> >>Kevin >> >>raid517 wrote: >> >> >> >> >>>>>Good news Kevin, it appears you are in the clear. >>>>> >>>>>I had a hunch and decided to not use Mplayer plugin and just try some >>>>>rapid browsing of the Apple site to see if I could make Firefox crash >>>>>under normal conditions. >>>>> >>>>>I quickly found that if I rapidly flipped back and forth between the >>>>>Apple movie trailer site and the Quicktime download page (with only a >>>>>single window open) withou waiting for either to fully load I could make >>>>>it crash fairly reliably. >>>>> >>>>>So I ran firefox from the command line and repeated the exercise. >>>>> >>>>>When the browser crashed it filled my console with a zillion error >>>>>messages (see attachment if curious) - which i think may be associated >>>>>with a fault in some graphics library or other that Firefox may be >>>>>using. (Just a wild guess though ATM). >>>>> >>>>>Well anyway this inspired me to try Mozilla Browser in place of Firefox >>>>>- and I am pleased to say that this does seem somewhat more stable. >>>>>(Not 100% because I can still make it crash, it just take a bit more >>>>>effort to do). >>>>> >>>>>So the bottom line is that the fault appears to be with the software on >>>>>my system - and not with your coding. :) >>>>> >>>>>It's a lot to ask I guess, but I don't suppose you can make any sense of >>>>>all of the junk messages that Firefox spits out before it dies? It would >>>>>just be helpful to know so that maybe I could pin my finger on something >>>>>definate for when I submit a bug to the Firefox devs. (Although given >>>>>the amount of time it can take for Firefox devs to fix problems, I am >>>>>not optomistic for a quick fix. Still if I report it as part of the beta >>>>>(since the latest beta also crashes) then who knows?). >>>>> >>>>>It is odd that you were (at one point) able to repeat this behaviour >>>>>too. It may just be a little more random and infrequent for you, so that >>>>>maybe your code was never really at fault to begin with? >>>>> >>>>> >>>>>GJ >>>>> >>>>> >>>>> >>>>> >>> >>> >- ------------------------------------------------------- >This SF.Net email is sponsored by: >Power Architecture Resource Center: Free content, downloads, discussions, >and more. http://solutions.newsforge.com/ibmarch.tmpl >_______________________________________________ >Mplayerplug-in-devel mailing list >Mpl...@li... >https://lists.sourceforge.net/lists/listinfo/mplayerplug-in-devel > > >>> >>> > > > > > > >-----BEGIN PGP SIGNATURE----- >Version: GnuPG v1.4.1 (GNU/Linux) > >iD8DBQFDWjVOaR60qN0tF+8RAgi3AJ9hvMJH8lFtmzxx608ObKnZ0oEVAgCfTVrP >rqhu6PFYCn4spym7mpxAHvw= >=6akw >-----END PGP SIGNATURE----- > > >------------------------------------------------------- >This SF.Net email is sponsored by: >Power Architecture Resource Center: Free content, downloads, discussions, >and more. http://solutions.newsforge.com/ibmarch.tmpl >_______________________________________________ >Mplayerplug-in-devel mailing list >Mpl...@li... >https://lists.sourceforge.net/lists/listinfo/mplayerplug-in-devel > > > > |
From: raid517 <ra...@uk...> - 2005-10-22 12:43:08
|
Hi Kevin, good news and bad I'm afraid. You seem to have hit the nail on the head. There doesn't seem to be any problem with Firefox after all. It appears to be a conflict between Mplayer Plugin and the GTK graphics library you mentioned. (Or at least it is certainly something in KDE). Since this is Linux thankfully we have several choices, so I opted to rerun the tests in both IceWM and fluxbox. I am pleased to report that all tests passed cleanly with no crashes. Logging back into KDE however, brought the problem back again. This is a little unfortunate as I freely admit I am a hard core KDE fan (with a smaller soft spot for Fluxbox) and have just spent the last several days building a new computer and installing and configuring (including theming) the perfect KDE system as a birthday gift for a young friend of mine. (I figured that if I take out all the hard work of setting up a Linux system for them, that they should really get along pretty well with it). Well anyway the point is I very much like KDE and I would like to continue using it - and i like the GTK theming support too as it lends consitancy to all of the apps on my desktop (I assume though that we are talking about the same thing here?). So I guess the question is, is there any possibility that you might be able to fix what does now after all appear to be a genuine bug? I think that is where the problem may have been... We were speaking two different languages. While I was talking KDE, you were talking fluxbox, or Gnome - or whatever other desktop you may currently be using. But it does now seem that the problem is isolated to an incompatability with KDE and Mplayer plugin. I hope this helps. GJ Kevin DeKorte wrote: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Well, I tried it we 3 different trailers in the setup you described and I can't get it to crash for me. And I don't experience the lag on loading. Kevin raid517 wrote: > Well that is depressing Kevin, because I actually have the latest CVS - > and I am still having problems. If it helps, the conditions you > described are somewhat different to what i described. > > A more detailed example might suffice: > > I am not a huge fan of tabbed browsing (yes I know it is against the > grain - but there you are as a linux user for the last 4 years I still > (as I supect do many people) default to the old IE behaviour of opening > new Windows when I want to keep a particular page open - but I also want > to navagate to another site). > > To this end to test this: > > Open 3 random new Firefox instances (as in don't use tabs). > > Use one of these Firefox browser windows to navagate to the Apple site. > > Play some HD content. (any resolution is fine). > > Let it play to the end. > > Close the Mplayer Plugin Window > > Now also close the Apple web page that you launched Mplayer plugin from > to watch your movie trailer. > > The result of this for me, is that the remaining two open windows crash > with a segefault. (The same one that I gave you in the firefox debug I > sent a few emails ago). > > Unfortunately the new code is also it seems occasionally causing Firefox > to hang on launch. The only way to overcome this is if I kill all > running firefox processes and then attempt to run it again. Uninstalling > the plugins overcomes this problem. > > I'm sorry to be a pain. I know you thought you had nailed it... > > GJ > > > Kevin DeKorte wrote: > > You'll know you have the change when the ChangeLog file has the > following lines at the top > > Make onMouseDown and onMouseUp actually work > Adding some locks back in and disable killmplayer function (causes a > long wait) > Fixed crash when you have two players on a page and browser window > closed > > SourceForge takes awhile to update it's anonymous CVS. But I have > checked it and it should be there. > > I did the following test and it didn't crash for me > > Open a browser and then open another browser window. In the second > window open the HD Harry Potter site (get 6 buttons) I click the 480p > button and wait for it to show the "Green Preview Screen" and then close > the second browser window and it closed correctly and the first window > remained running. It had something to do with two plugins being loaded, > because if I do it with only one plugin it does not crash. Which is > interesting in itself, because the plugins should be isolated from each > other. Except for global variables of which I have two errno (libc > standard) and DEBUG which is mainly a readonly variable and if it is > modified nothing cares. > > Prior to the patch, this test did not succeed for me. > > Kevin > > > raid517 wrote: > > > > >>>> Kevin I tried the newest CVS code as of 11:30pm London time. I'm >>>> assuming that your fixes haven't been commited yet as I am still >>>> having >>>> the same problem. I am sure it has something to do with the way the HD >>>> movie buttons are displayed on the Apple web site, because if I >>>> navagate >>>> away from that particular web page when a movie finishes playing, I >>>> can >>>> avoid a crash. >>>> >>>> I am not sure if this counts as useful information or not. >>>> >>>> I will try CVS again tomorrow. :) >>>> >>>> GJ >>>> >>>> >>>> ------------------------------------------------------- >>>> This SF.Net email is sponsored by: >>>> Power Architecture Resource Center: Free content, downloads, >>>> discussions, >>>> and more. http://solutions.newsforge.com/ibmarch.tmpl >>>> _______________________________________________ >>>> Mplayerplug-in-devel mailing list >>>> Mpl...@li... >>>> https://lists.sourceforge.net/lists/listinfo/mplayerplug-in-devel >>>> >>>> >>>> >>> > > >> > - ------------------------------------------------------- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl _______________________________________________ Mplayerplug-in-devel mailing list Mpl...@li... https://lists.sourceforge.net/lists/listinfo/mplayerplug-in-devel >> > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDWYRcaR60qN0tF+8RAni4AJ0UW4t/Qxpn+mdmRLddZE9mDcBdrwCglsRU VlYOYawFHhvuBAHJozM/p/8= =NuMV -----END PGP SIGNATURE----- ------------------------------------------------------- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl _______________________________________________ Mplayerplug-in-devel mailing list Mpl...@li... https://lists.sourceforge.net/lists/listinfo/mplayerplug-in-devel |
From: Kevin D. <kde...@ya...> - 2005-10-19 12:25:42
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Ok, Well that command I gave you was pretty much the actual command that mplayerplug-in uses. So lets do a recap 1. If you use a .deb of mplayerplug-in assuming 3.05 then everything works except Apple HD support sucks, but when you use a self compiled version of mplayerplug-in nothing works. 2. mplayer is in your path (good) 3. the command line tests all work (good) 4. the command line test I gave you works (good) 5. codecs appear to be installed 6. playing from the command line works Any other info? Did you remove mplayerplug-in.deb file before you installed the self compiled version? If this is the case, it sounds like the self compiled version is messed up. Kevin raid517 wrote: > > Hi Kevin, thanks for your help in this matter. I can tell you that the > command (minus the extra -) works - but that the video plays very > slowly. I'm not sure if it is network traffic on sourceforge (it's not > at my end as i have an 8Mbs connection) so i will try again a little > later and let you know. > > Best regards, > > GJ > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDVjs3aR60qN0tF+8RAtVMAJ9t6qnOX2mtG9BMo2MiC6lyB2e9MgCgzLhg j5Mf37wkj5qV8yMplxZYenI= =TVB9 -----END PGP SIGNATURE----- |
From: raid517 <ra...@uk...> - 2005-10-19 13:53:34
|
Well no, that's it. No more info. The deb builds fine. I have even mailed you info concerning the exact options I used. I also uniosntalled all previous bersions of the plugin before installing this one. However, one last test I can do is to uninstall again and build the plugin completely from source. (No .deb) Is there possibly a prefered GCC compiler version I should use? GJ Kevin DeKorte wrote: >-----BEGIN PGP SIGNED MESSAGE----- >Hash: SHA1 > >Ok, > >Well that command I gave you was pretty much the actual command that >mplayerplug-in uses. So lets do a recap > >1. If you use a .deb of mplayerplug-in assuming 3.05 then everything >works except Apple HD support sucks, but when you use a self compiled >version of mplayerplug-in nothing works. > >2. mplayer is in your path (good) > >3. the command line tests all work (good) > >4. the command line test I gave you works (good) > >5. codecs appear to be installed > >6. playing from the command line works > >Any other info? > >Did you remove mplayerplug-in.deb file before you installed the self >compiled version? > >If this is the case, it sounds like the self compiled version is messed up. > > >Kevin > > >raid517 wrote: > > >>Hi Kevin, thanks for your help in this matter. I can tell you that the >>command (minus the extra -) works - but that the video plays very >>slowly. I'm not sure if it is network traffic on sourceforge (it's not >>at my end as i have an 8Mbs connection) so i will try again a little >>later and let you know. >> >>Best regards, >> >>GJ >> >> >> >-----BEGIN PGP SIGNATURE----- >Version: GnuPG v1.4.1 (GNU/Linux) > >iD8DBQFDVjs3aR60qN0tF+8RAtVMAJ9t6qnOX2mtG9BMo2MiC6lyB2e9MgCgzLhg >j5Mf37wkj5qV8yMplxZYenI= >=TVB9 >-----END PGP SIGNATURE----- > > >------------------------------------------------------- >This SF.Net email is sponsored by: >Power Architecture Resource Center: Free content, downloads, discussions, >and more. http://solutions.newsforge.com/ibmarch.tmpl >_______________________________________________ >Mplayerplug-in-devel mailing list >Mpl...@li... >https://lists.sourceforge.net/lists/listinfo/mplayerplug-in-devel > > > > |
From: Kevin D. <kde...@ya...> - 2005-10-19 14:06:42
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 You should use the compiler that mozilla is compiled with. You can get that by typing "about:buildconfig" in the browser location field (where you type url's) Can you do this for me... for mplayerplug-in make clean ./configure And send me the output from that... I want to see what configure is seeing on your machine. Kevin raid517 wrote: > Well no, that's it. No more info. The deb builds fine. I have even > mailed you info concerning the exact options I used. I also uniosntalled > all previous bersions of the plugin before installing this one. However, > one last test I can do is to uninstall again and build the plugin > completely from source. (No .deb) Is there possibly a prefered GCC > compiler version I should use? > > GJ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDVlLWaR60qN0tF+8RAnE6AJ94x2Pio3SxS35lA7BMh98vXtvh7gCcCHZz pcNnLC6InTQhABzjRM29rZg= =izVo -----END PGP SIGNATURE----- |
From: raid517 <ra...@uk...> - 2005-10-19 14:27:28
|
As requested: ./configure checking for g++... g++ checking for C++ compiler default output file name... a.out checking whether the C++ compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C++ compiler... yes checking whether g++ accepts -g... yes checking for gcc... gcc checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ANSI C... none needed checking for a BSD-compatible install... /usr/bin/install -c checking for gawk... gawk checking whether make sets $(MAKE)... yes configure: Determining mozilla/firefox packages to link against checking for pkg-config... /usr/bin/pkg-config checking for mozilla-plugin... yes checking MOZPLUG_CFLAGS... -I/usr/include/mozilla/java -I/usr/include/mozilla/plugin -I/usr/include/mozilla -I/usr/include/mozilla/xpcom -I/usr/include/mozilla/string -I/usr/include/mozilla/nspr checking MOZPLUG_LIBS... -L/usr/lib/mozilla -lxpcom -lplds4 -lplc4 -lnspr4 -ldl -lc -lpthread checking for gtk+-2.0... yes checking GTK_CFLAGS... -DXTHREADS -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/X11R6/include -I/usr/include/atk-1.0 -I/usr/include/pango-1.0 -I/usr/include/freetype2 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include checking GTK_LIBS... -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lgdk_pixbuf-2.0 -lm -lpangoxft-1.0 -lpangox-1.0 -lpangoft2-1.0 -lpango-1.0 -lgobject-2.0 -lgmodule-2.0 -ldl -lglib-2.0 checking for gthread-2.0... yes checking GTHREAD_CFLAGS... -pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include checking GTHREAD_LIBS... -pthread -lgthread-2.0 -lglib-2.0 checking how to run the C preprocessor... gcc -E checking for X... libraries /usr/X11R6/lib, headers /usr/X11R6/include checking for gethostbyname... yes checking for connect... yes checking for remove... yes checking for shmat... yes checking for IceConnectionNumber in -lICE... yes checking for egrep... grep -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking stddef.h usability... yes checking stddef.h presence... yes checking for stddef.h... yes checking for stdlib.h... (cached) yes checking for unistd.h... (cached) yes checking X11/Xlib.h usability... yes checking X11/Xlib.h presence... yes checking for X11/Xlib.h... yes checking X11/Intrinsic.h usability... yes checking X11/Intrinsic.h presence... yes checking for X11/Intrinsic.h... yes checking X11/StringDefs.h usability... yes checking X11/StringDefs.h presence... yes checking for X11/StringDefs.h... yes checking for sys/stat.h... (cached) yes checking fcntl.h usability... yes checking fcntl.h presence... yes checking for fcntl.h... yes checking for an ANSI C-conforming const... yes checking whether time.h and sys/time.h may both be included... yes checking for pid_t... yes checking for size_t... yes checking for stdlib.h... (cached) yes checking for GNU libc compatible malloc... yes checking for unistd.h... (cached) yes checking vfork.h usability... no checking vfork.h presence... no checking for vfork.h... no checking for fork... yes checking for vfork... yes checking for working fork... yes checking for working vfork... (cached) yes checking for memset... yes checking for strcasecmp... yes checking for strchr... yes checking for strdup... yes checking for strncasecmp... yes checking for strstr... yes checking for strrchr... yes checking for snprintf... yes checking for mkfifo... yes checking for dup2... yes checking for gettimeofday... yes checking for strerror... yes checking for strtol... yes checking for memmem... yes checking libintl.h usability... yes checking libintl.h presence... yes checking for libintl.h... yes checking sys/time.h usability... yes checking sys/time.h presence... yes checking for sys/time.h... yes checking sys/param.h usability... yes checking sys/param.h presence... yes checking for sys/param.h... yes checking for stdbool.h that conforms to C99... yes checking for _Bool... yes checking for sys/wait.h that is POSIX.1 compatible... yes checking return type of signal handlers... void checking X11/xpm.h usability... yes checking X11/xpm.h presence... yes checking for X11/xpm.h... yes checking for DPMSQueryExtension in -lXdpms... no checking for X11/extensions/dpms.h... yes configure: creating ./config.status config.status: creating Makefile config.status: creating po/Makefile config.status: creating install.sh config.status: creating config.h Kevin DeKorte wrote: >-----BEGIN PGP SIGNED MESSAGE----- >Hash: SHA1 > >You should use the compiler that mozilla is compiled with. You can get >that by typing "about:buildconfig" in the browser location field (where >you type url's) > >Can you do this for me... > >for mplayerplug-in > >make clean >./configure > >And send me the output from that... I want to see what configure is >seeing on your machine. > >Kevin > >raid517 wrote: > > >>Well no, that's it. No more info. The deb builds fine. I have even >>mailed you info concerning the exact options I used. I also uniosntalled >>all previous bersions of the plugin before installing this one. However, >>one last test I can do is to uninstall again and build the plugin >>completely from source. (No .deb) Is there possibly a prefered GCC >>compiler version I should use? >> >>GJ >> >> > > > >-----BEGIN PGP SIGNATURE----- >Version: GnuPG v1.4.1 (GNU/Linux) > >iD8DBQFDVlLWaR60qN0tF+8RAnE6AJ94x2Pio3SxS35lA7BMh98vXtvh7gCcCHZz >pcNnLC6InTQhABzjRM29rZg= >=izVo >-----END PGP SIGNATURE----- > > >------------------------------------------------------- >This SF.Net email is sponsored by: >Power Architecture Resource Center: Free content, downloads, discussions, >and more. http://solutions.newsforge.com/ibmarch.tmpl >_______________________________________________ >Mplayerplug-in-devel mailing list >Mpl...@li... >https://lists.sourceforge.net/lists/listinfo/mplayerplug-in-devel > > > > |
From: Kevin D. <kde...@ya...> - 2005-10-19 14:54:41
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Well, that looks really good, so when you make and then make install that code does it work? Don't need to rerun configure as it looks good. Kevin raid517 wrote: > As requested: > > ./configure > checking for g++... g++ > checking for C++ compiler default output file name... a.out > checking whether the C++ compiler works... yes > checking whether we are cross compiling... no > checking for suffix of executables... > checking for suffix of object files... o > checking whether we are using the GNU C++ compiler... yes > checking whether g++ accepts -g... yes > checking for gcc... gcc > checking whether we are using the GNU C compiler... yes > checking whether gcc accepts -g... yes > checking for gcc option to accept ANSI C... none needed > checking for a BSD-compatible install... /usr/bin/install -c > checking for gawk... gawk > checking whether make sets $(MAKE)... yes > configure: Determining mozilla/firefox packages to link against > checking for pkg-config... /usr/bin/pkg-config > checking for mozilla-plugin... yes > checking MOZPLUG_CFLAGS... -I/usr/include/mozilla/java > -I/usr/include/mozilla/plugin -I/usr/include/mozilla > -I/usr/include/mozilla/xpcom -I/usr/include/mozilla/string > -I/usr/include/mozilla/nspr > checking MOZPLUG_LIBS... -L/usr/lib/mozilla -lxpcom -lplds4 -lplc4 > -lnspr4 -ldl -lc -lpthread > checking for gtk+-2.0... yes > checking GTK_CFLAGS... -DXTHREADS -I/usr/include/gtk-2.0 > -I/usr/lib/gtk-2.0/include -I/usr/X11R6/include -I/usr/include/atk-1.0 > -I/usr/include/pango-1.0 -I/usr/include/freetype2 > -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include > checking GTK_LIBS... -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 > -lgdk_pixbuf-2.0 -lm -lpangoxft-1.0 -lpangox-1.0 -lpangoft2-1.0 > -lpango-1.0 -lgobject-2.0 -lgmodule-2.0 -ldl -lglib-2.0 > checking for gthread-2.0... yes > checking GTHREAD_CFLAGS... -pthread -I/usr/include/glib-2.0 > -I/usr/lib/glib-2.0/include > checking GTHREAD_LIBS... -pthread -lgthread-2.0 -lglib-2.0 > checking how to run the C preprocessor... gcc -E > checking for X... libraries /usr/X11R6/lib, headers /usr/X11R6/include > checking for gethostbyname... yes > checking for connect... yes > checking for remove... yes > checking for shmat... yes > checking for IceConnectionNumber in -lICE... yes > checking for egrep... grep -E > checking for ANSI C header files... yes > checking for sys/types.h... yes > checking for sys/stat.h... yes > checking for stdlib.h... yes > checking for string.h... yes > checking for memory.h... yes > checking for strings.h... yes > checking for inttypes.h... yes > checking for stdint.h... yes > checking for unistd.h... yes > checking stddef.h usability... yes > checking stddef.h presence... yes > checking for stddef.h... yes > checking for stdlib.h... (cached) yes > checking for unistd.h... (cached) yes > checking X11/Xlib.h usability... yes > checking X11/Xlib.h presence... yes > checking for X11/Xlib.h... yes > checking X11/Intrinsic.h usability... yes > checking X11/Intrinsic.h presence... yes > checking for X11/Intrinsic.h... yes > checking X11/StringDefs.h usability... yes > checking X11/StringDefs.h presence... yes > checking for X11/StringDefs.h... yes > checking for sys/stat.h... (cached) yes > checking fcntl.h usability... yes > checking fcntl.h presence... yes > checking for fcntl.h... yes > checking for an ANSI C-conforming const... yes > checking whether time.h and sys/time.h may both be included... yes > checking for pid_t... yes > checking for size_t... yes > checking for stdlib.h... (cached) yes > checking for GNU libc compatible malloc... yes > checking for unistd.h... (cached) yes > checking vfork.h usability... no > checking vfork.h presence... no > checking for vfork.h... no > checking for fork... yes > checking for vfork... yes > checking for working fork... yes > checking for working vfork... (cached) yes > checking for memset... yes > checking for strcasecmp... yes > checking for strchr... yes > checking for strdup... yes > checking for strncasecmp... yes > checking for strstr... yes > checking for strrchr... yes > checking for snprintf... yes > checking for mkfifo... yes > checking for dup2... yes > checking for gettimeofday... yes > checking for strerror... yes > checking for strtol... yes > checking for memmem... yes > checking libintl.h usability... yes > checking libintl.h presence... yes > checking for libintl.h... yes > checking sys/time.h usability... yes > checking sys/time.h presence... yes > checking for sys/time.h... yes > checking sys/param.h usability... yes > checking sys/param.h presence... yes > checking for sys/param.h... yes > checking for stdbool.h that conforms to C99... yes > checking for _Bool... yes > checking for sys/wait.h that is POSIX.1 compatible... yes > checking return type of signal handlers... void > checking X11/xpm.h usability... yes > checking X11/xpm.h presence... yes > checking for X11/xpm.h... yes > checking for DPMSQueryExtension in -lXdpms... no > checking for X11/extensions/dpms.h... yes > configure: creating ./config.status > config.status: creating Makefile > config.status: creating po/Makefile > config.status: creating install.sh > config.status: creating config.h > > Kevin DeKorte wrote: > > You should use the compiler that mozilla is compiled with. You can get > that by typing "about:buildconfig" in the browser location field (where > you type url's) > > Can you do this for me... > > for mplayerplug-in > > make clean > ./configure > > And send me the output from that... I want to see what configure is > seeing on your machine. > > Kevin > > raid517 wrote: > > >>>> Well no, that's it. No more info. The deb builds fine. I have even >>>> mailed you info concerning the exact options I used. I also uniosntalled >>>> all previous bersions of the plugin before installing this one. However, >>>> one last test I can do is to uninstall again and build the plugin >>>> completely from source. (No .deb) Is there possibly a prefered GCC >>>> compiler version I should use? >>>> >>>> GJ >>>> > > > > >> >> - ------------------------------------------------------- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl _______________________________________________ Mplayerplug-in-devel mailing list Mpl...@li... https://lists.sourceforge.net/lists/listinfo/mplayerplug-in-devel >> >> >> -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDVl4jaR60qN0tF+8RAuqhAJ9u/V8Dl15ucmPV8sZHcK2IVaO+DACgzlFr S3308V1HeHtlGdFHYYXvWnc= =5rSJ -----END PGP SIGNATURE----- |
From: raid517 <ra...@uk...> - 2005-10-19 16:17:10
|
Well after I run make and make install - I basically just get the same outcome. Mplayer Plugin tries to buffer 100% of the movie (which is essentially the same as just downloading the whole movie - which again kind of defeats the point of having streaming media) and then after it has done this, it just sits there and does nothing. An example is this link (indeed Yahoo video search is a very good testing ground for all kinds of streaming media types) http://video.search.yahoo.com/search/video?ei=UTF-8&fr=sfp&p=funny, I can't get any of the videos here to play, or to 'stream' properly. (However I can play all of these links locally on my computer through Mplayer, or gmplayer) The only option I think I have left is if someone can produce a .deb for me to test that is built for Debian unstable that they know for 100% sure is working on their system. In other words, the only option I can think of is that maybe something in the compile process on my system is broken. But I won't know this until I have a working precompiled .deb I can test. GJ Kevin DeKorte wrote: >-----BEGIN PGP SIGNED MESSAGE----- >Hash: SHA1 > >Well, that looks really good, so when you make and then make install >that code does it work? Don't need to rerun configure as it looks good. > >Kevin > > >raid517 wrote: > > >>As requested: >> >>./configure >>checking for g++... g++ >>checking for C++ compiler default output file name... a.out >>checking whether the C++ compiler works... yes >>checking whether we are cross compiling... no >>checking for suffix of executables... >>checking for suffix of object files... o >>checking whether we are using the GNU C++ compiler... yes >>checking whether g++ accepts -g... yes >>checking for gcc... gcc >>checking whether we are using the GNU C compiler... yes >>checking whether gcc accepts -g... yes >>checking for gcc option to accept ANSI C... none needed >>checking for a BSD-compatible install... /usr/bin/install -c >>checking for gawk... gawk >>checking whether make sets $(MAKE)... yes >>configure: Determining mozilla/firefox packages to link against >>checking for pkg-config... /usr/bin/pkg-config >>checking for mozilla-plugin... yes >>checking MOZPLUG_CFLAGS... -I/usr/include/mozilla/java >>-I/usr/include/mozilla/plugin -I/usr/include/mozilla >>-I/usr/include/mozilla/xpcom -I/usr/include/mozilla/string >>-I/usr/include/mozilla/nspr >>checking MOZPLUG_LIBS... -L/usr/lib/mozilla -lxpcom -lplds4 -lplc4 >>-lnspr4 -ldl -lc -lpthread >>checking for gtk+-2.0... yes >>checking GTK_CFLAGS... -DXTHREADS -I/usr/include/gtk-2.0 >>-I/usr/lib/gtk-2.0/include -I/usr/X11R6/include -I/usr/include/atk-1.0 >>-I/usr/include/pango-1.0 -I/usr/include/freetype2 >>-I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include >>checking GTK_LIBS... -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 >>-lgdk_pixbuf-2.0 -lm -lpangoxft-1.0 -lpangox-1.0 -lpangoft2-1.0 >>-lpango-1.0 -lgobject-2.0 -lgmodule-2.0 -ldl -lglib-2.0 >>checking for gthread-2.0... yes >>checking GTHREAD_CFLAGS... -pthread -I/usr/include/glib-2.0 >>-I/usr/lib/glib-2.0/include >>checking GTHREAD_LIBS... -pthread -lgthread-2.0 -lglib-2.0 >>checking how to run the C preprocessor... gcc -E >>checking for X... libraries /usr/X11R6/lib, headers /usr/X11R6/include >>checking for gethostbyname... yes >>checking for connect... yes >>checking for remove... yes >>checking for shmat... yes >>checking for IceConnectionNumber in -lICE... yes >>checking for egrep... grep -E >>checking for ANSI C header files... yes >>checking for sys/types.h... yes >>checking for sys/stat.h... yes >>checking for stdlib.h... yes >>checking for string.h... yes >>checking for memory.h... yes >>checking for strings.h... yes >>checking for inttypes.h... yes >>checking for stdint.h... yes >>checking for unistd.h... yes >>checking stddef.h usability... yes >>checking stddef.h presence... yes >>checking for stddef.h... yes >>checking for stdlib.h... (cached) yes >>checking for unistd.h... (cached) yes >>checking X11/Xlib.h usability... yes >>checking X11/Xlib.h presence... yes >>checking for X11/Xlib.h... yes >>checking X11/Intrinsic.h usability... yes >>checking X11/Intrinsic.h presence... yes >>checking for X11/Intrinsic.h... yes >>checking X11/StringDefs.h usability... yes >>checking X11/StringDefs.h presence... yes >>checking for X11/StringDefs.h... yes >>checking for sys/stat.h... (cached) yes >>checking fcntl.h usability... yes >>checking fcntl.h presence... yes >>checking for fcntl.h... yes >>checking for an ANSI C-conforming const... yes >>checking whether time.h and sys/time.h may both be included... yes >>checking for pid_t... yes >>checking for size_t... yes >>checking for stdlib.h... (cached) yes >>checking for GNU libc compatible malloc... yes >>checking for unistd.h... (cached) yes >>checking vfork.h usability... no >>checking vfork.h presence... no >>checking for vfork.h... no >>checking for fork... yes >>checking for vfork... yes >>checking for working fork... yes >>checking for working vfork... (cached) yes >>checking for memset... yes >>checking for strcasecmp... yes >>checking for strchr... yes >>checking for strdup... yes >>checking for strncasecmp... yes >>checking for strstr... yes >>checking for strrchr... yes >>checking for snprintf... yes >>checking for mkfifo... yes >>checking for dup2... yes >>checking for gettimeofday... yes >>checking for strerror... yes >>checking for strtol... yes >>checking for memmem... yes >>checking libintl.h usability... yes >>checking libintl.h presence... yes >>checking for libintl.h... yes >>checking sys/time.h usability... yes >>checking sys/time.h presence... yes >>checking for sys/time.h... yes >>checking sys/param.h usability... yes >>checking sys/param.h presence... yes >>checking for sys/param.h... yes >>checking for stdbool.h that conforms to C99... yes >>checking for _Bool... yes >>checking for sys/wait.h that is POSIX.1 compatible... yes >>checking return type of signal handlers... void >>checking X11/xpm.h usability... yes >>checking X11/xpm.h presence... yes >>checking for X11/xpm.h... yes >>checking for DPMSQueryExtension in -lXdpms... no >>checking for X11/extensions/dpms.h... yes >>configure: creating ./config.status >>config.status: creating Makefile >>config.status: creating po/Makefile >>config.status: creating install.sh >>config.status: creating config.h >> >>Kevin DeKorte wrote: >> >>You should use the compiler that mozilla is compiled with. You can get >>that by typing "about:buildconfig" in the browser location field (where >>you type url's) >> >>Can you do this for me... >> >>for mplayerplug-in >> >>make clean >>./configure >> >>And send me the output from that... I want to see what configure is >>seeing on your machine. >> >>Kevin >> >>raid517 wrote: >> >> >> >> >>>>>Well no, that's it. No more info. The deb builds fine. I have even >>>>>mailed you info concerning the exact options I used. I also uniosntalled >>>>>all previous bersions of the plugin before installing this one. However, >>>>>one last test I can do is to uninstall again and build the plugin >>>>>completely from source. (No .deb) Is there possibly a prefered GCC >>>>>compiler version I should use? >>>>> >>>>>GJ >>>>> >>>>> >>>>> >> >> >> >> >>> >>> >- ------------------------------------------------------- >This SF.Net email is sponsored by: >Power Architecture Resource Center: Free content, downloads, discussions, >and more. http://solutions.newsforge.com/ibmarch.tmpl >_______________________________________________ >Mplayerplug-in-devel mailing list >Mpl...@li... >https://lists.sourceforge.net/lists/listinfo/mplayerplug-in-devel > > >>> >>> > > > > > > >-----BEGIN PGP SIGNATURE----- >Version: GnuPG v1.4.1 (GNU/Linux) > >iD8DBQFDVl4jaR60qN0tF+8RAuqhAJ9u/V8Dl15ucmPV8sZHcK2IVaO+DACgzlFr >S3308V1HeHtlGdFHYYXvWnc= >=5rSJ >-----END PGP SIGNATURE----- > > >------------------------------------------------------- >This SF.Net email is sponsored by: >Power Architecture Resource Center: Free content, downloads, discussions, >and more. http://solutions.newsforge.com/ibmarch.tmpl >_______________________________________________ >Mplayerplug-in-devel mailing list >Mpl...@li... >https://lists.sourceforge.net/lists/listinfo/mplayerplug-in-devel > > > > |