crash on firefox

Help
klades
2005-09-03
2013-05-13
  • klades
    klades
    2005-09-03

    Hello to everybody, i'm new on this list.
    I want to notice that in my experience mplayerplug-in works very well with Firefox, but makes it very unstable.
    This happens especially (but not only in this case) if I stop a video and then close or change the page: when I do it, Firefox crashes very often when you click on a form, or try to open the panel preferences or any other panel.
    I notice this problem with several versions of Mplayerplug-in (from the 1.x versions to the 3.05), Firefox (build with gtk1 and with gtk2, from the 0.8 version to the 1.0.6) and Mplayer (from 0.92 1.0pre7). This happened on my debian woody (glibc 2.2.4) and also go on happening on the actual debian sarge (glibc 2.3.2).
    Running Firefox with the -g flag, I see this at the moment of the crash:

    Program received signal SIGSEGV, Segmentation fault.
    [Switching to Thread -1222485072 (LWP 9879)]
    0xb340a7d0 in ?? ()

    The last number, the memory location, can be different each time.
    Please tell me how this problem could be fixed, because it's very very heavy...
    I use the italian locale on the o.s and in Firefox.
    Thanks for your help, Paolo

     
    • klades
      klades
      2005-09-03

      I add the output of gdb bt after a crash

      (gdb) bt
      #0  0xb3c587d0 in ?? ()
      #1  <signal handler called>
      #2  0xb7656523 in poll () from /lib/tls/libc.so.6
      #3  0xb7a172b6 in g_main_loop_get_context () from /usr/lib/libglib-2.0.so.0
      #4  0xb7a168b0 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
      #5  0xb7a16ed3 in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
      #6  0xb7cc7bb3 in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0
      #7  0x08213c34 in nsReadingIterator<unsigned short>::advance ()
      #8  0x085d5d93 in nsPRUint32Key::Clone ()
      #9  0x0878135c in nsPRUint32Key::Clone ()
      #10 0x08073ae3 in ?? ()
      #11 0x00000001 in ?? ()
      #12 0xbffff6e4 in ?? ()
      #13 0x0879ce88 in _IO_stdin_used ()
      #14 0xbffff6b8 in ?? ()
      #15 0xb759c974 in __libc_start_main () from /lib/tls/libc.so.6
      #16 0xb759c974 in __libc_start_main () from /lib/tls/libc.so.6
      #17 0x08073a41 in ?? ()

       
      • Kevin DeKorte
        Kevin DeKorte
        2005-09-03

        Nothing in that backtrace points to mplayerplug-in. Perhaps you have a url and a process you can duplicate?

        Like

        1. Got to this URL
        2. Watch 5 seconds of video.
        3. Open the History Panel
        4. Crash...

         
        • klades
          klades
          2005-09-03

          I found a way to reproduce at 100% the crash:

          1. go at http://fredrik.hubbe.net/plugger/test.mpg
          2. play the video for some seconds
          3. click on the homepage button, without stopping the video
          4. when the homepage is shown, click on Edit --> Preferences
          5. crash

          If I follow the same steps in debug mode, the crash happens at point number 3, call to the homepage, with the following backtrace:

          Program received signal SIGTRAP, Trace/breakpoint trap.
          [Switching to Thread -1220287328 (LWP 5113)]
          0xb7ff6783 in _dl_debug_state () from /lib/ld-linux.so.2
          (gdb) bt
          #0  0xb7ff6783 in _dl_debug_state () from /lib/ld-linux.so.2
          #1  0xb7ff6266 in _dl_init () from /lib/ld-linux.so.2
          #2  0xb768f2b2 in _dl_open () from /lib/tls/libc.so.6
          #3  0xb7ff6016 in _dl_catch_error () from /lib/ld-linux.so.2
          #4  0xb768eed6 in _dl_open () from /lib/tls/libc.so.6
          #5  0xb7690d63 in __libc_dlclose () from /lib/tls/libc.so.6
          #6  0xb7ff6016 in _dl_catch_error () from /lib/ld-linux.so.2
          #7  0xb7690be8 in __libc_dlopen_mode () from /lib/tls/libc.so.6
          #8  0xb7e95218 in pthread_cancel_init () from /lib/tls/libpthread.so.0
          #9  0xb7e91e8c in pthread_cancel () from /lib/tls/libpthread.so.0
          #10 0xb42d3774 in nsPluginInstance::shutdown (this=0x91fa358)
              at Source/plugin.cpp:361
          #11 0xb42d3116 in nsPluginInstance::shut (this=0x91fa358)
              at Source/plugin.cpp:337
          #12 0xb42da751 in NPP_Destroy (instance=0xb8000ec4, save=0xbfffe9b8)
              at plugingate/npp_gate.cpp:86
          #13 0x081ee258 in nsReadingIterator<unsigned short>::advance ()
          #14 0x0842e025 in nsPRUint32Key::Clone ()
          #15 0x08428a1d in nsPRUint32Key::Clone ()
          #16 0x0841387b in nsPRUint32Key::Clone ()
          #17 0x08428a1d in nsPRUint32Key::Clone ()
          #18 0x0841387b in nsPRUint32Key::Clone ()
          #19 0x082a5844 in nsReadingIterator<unsigned short>::advance ()
          ---Type <return> to continue, or q <return> to quit---
          #20 0x0841e627 in nsPRUint32Key::Clone ()
          #21 0x0842353d in nsPRUint32Key::Clone ()
          #22 0x082a5844 in nsReadingIterator<unsigned short>::advance ()
          #23 0x0841e627 in nsPRUint32Key::Clone ()
          #24 0x08278352 in nsReadingIterator<unsigned short>::advance ()
          #25 0x082a5844 in nsReadingIterator<unsigned short>::advance ()
          #26 0x0841e627 in nsPRUint32Key::Clone ()
          #27 0x08278352 in nsReadingIterator<unsigned short>::advance ()
          #28 0x082a5844 in nsReadingIterator<unsigned short>::advance ()
          #29 0x0841e627 in nsPRUint32Key::Clone ()
          #30 0x08220681 in nsReadingIterator<unsigned short>::advance ()
          #31 0x0822a3fb in nsReadingIterator<unsigned short>::advance ()
          #32 0x082c302d in nsReadingIterator<unsigned short>::advance ()
          #33 0x082c363a in nsReadingIterator<unsigned short>::advance ()
          #34 0x0823047e in nsReadingIterator<unsigned short>::advance ()
          #35 0x08230562 in nsReadingIterator<unsigned short>::advance ()
          #36 0x0822ca51 in nsReadingIterator<unsigned short>::advance ()
          #37 0xb7f4cf0d in nsTimerImpl::Fire () from /usr/local/firefox/libxpcom.so
          #38 0xb7f4cf68 in handleTimerEvent () from /usr/local/firefox/libxpcom.so
          #39 0xb7f49853 in PL_HandleEvent () from /usr/local/firefox/libxpcom.so
          #40 0xb7f497a6 in PL_ProcessPendingEvents ()
             from /usr/local/firefox/libxpcom.so
          #41 0xb7f4add3 in nsEventQueueImpl::NotifyObservers ()
          ---Type <return> to continue, or q <return> to quit---
             from /usr/local/firefox/libxpcom.so
          #42 0x08213988 in nsReadingIterator<unsigned short>::advance ()
          #43 0xb7a3adbf in g_vasprintf () from /usr/lib/libglib-2.0.so.0
          #44 0xb7a15582 in g_main_depth () from /usr/lib/libglib-2.0.so.0
          #45 0xb7a165f8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
          #46 0xb7a16930 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
          #47 0xb7a16ed3 in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
          #48 0xb7cc7bb3 in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0
          #49 0x08213c34 in nsReadingIterator<unsigned short>::advance ()
          #50 0x085d5d93 in nsPRUint32Key::Clone ()
          #51 0x0878135c in nsPRUint32Key::Clone ()
          #52 0x08073ae3 in ?? ()
          #53 0x00000001 in ?? ()
          #54 0xbffff6e4 in ?? ()
          #55 0x0879ce88 in _IO_stdin_used ()
          #56 0xbffff6b8 in ?? ()
          #57 0xb759c974 in __libc_start_main () from /lib/tls/libc.so.6
          #58 0xb759c974 in __libc_start_main () from /lib/tls/libc.so.6
          #59 0x08073a41 in ?? ()

          Notice that the change of webpage without stopping the video makes the browser much more instable, but I've crashes, not reproducible at the moment, also if I stop.

           
    • Kevin DeKorte
      Kevin DeKorte
      2005-09-03

      Unable to duplicate this crash on Fedora Core 3 or Ubuntu Breezy. What the problem looks like to me is that mplayer is not shutting down properly. You might try getting mplayer 1.0pre7 or even CVS (that is what I use)

      You also might try commenting out the line

      status = kill(instance->pid, 9)

      in plugin-support.cpp around line 557

      This might leave a couple of mplayer's running in suspended state however. And if you are seeing this, it is very likely a problem with your thread libraries and/or your copy of mplayer.

      You also might try mplayerplug-in CVS and see if you get any different results.

       
    • klades
      klades
      2005-09-03

      With every version of Mplayer/Mplayerplug-in I get the same crashes.

      I've searched in the Debian website and I found that it seems to be a bug (?) of Debian glibc: see
      http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=275240

      The problem is that on Debian Sarge it's impossibile to upgrade the  glibc to 2.3.5 version.
      I sent a new bug report to Debian: we'll see if they will fix the problem also for Sarge (I doubt...), but I wonder if the developers of Mplayerplug-in could try to make the plugin fully compatible also with the Debian Sarge glibc.
      Thanks for the attention.

       
    • klades
      klades
      2005-09-18

      Still me...I've made some tests and I discovered that the crash happens only if I have also "plugger" installed, so there some conflict between them. I've seen that with "mozplugger" the conflicts is even bigger, infact the browser crashes suddendly.
      Now I've unistalled "plugger" and I'm not having crash anymore (I hope!!!).
      It'd be interesting to know if there some other user that has crash problems with mplayerplug-in beacuse of the presence of plugger or mozplugger.

       
    • klades
      klades
      2005-09-19

      Without plugger, Firefox doesn't crash with the steps I wrote, but crashes the same...so I must think that mplayerplug-in is not compatible with Debian Sarge.

       
    • klades
      klades
      2006-05-04

      After a long testing, I can say that at least the problem has been fixed on Debian Sarge!!!

      I've had no crash anymore, using Firefox 1.5 or higher and Mplayerplug-in 3.17 and higher.

      I don't know which of these two updates has fixed (I suspect Firefox, but I'm not sure at all), but I can say that with this combination it works!!!
      Thanks to everybody, Paolo