Firefox flash problems (npviewer.bin crashed with SIGSEGV [with attached backtrace])

[Martin Gerdzhev]

Binary package hint: nspluginwrapper

Npviewer crashes all the time when surfing websites that have any flash content. Even sites like yahoo mail and hotmail cause it to crash. This is on an up-to-date Intrepid 64 bit.

ProblemType: Crash
Architecture: amd64
Disassembly: 0xf78e39f0:
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/lib/nspluginwrapper/i386/linux/npviewer.bin
Package: nspluginwrapper 1.1.0-0ubuntu2
ProcAttrCurrent: unconfined
ProcCmdline: /usr/lib/nspluginwrapper/i386/linux/npviewer.bin --plugin /usr/lib/flashplugin-nonfree/libflashplayer.so --connection /org/wrapper/NSPlugins/libflashplayer.so/8371-6
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: nspluginwrapper
Stacktrace: #0 0xf78e39f0 in ?? ()
StacktraceTop: ?? ()
ThreadStacktrace:

Title: npviewer.bin crashed with SIGSEGV
Uname: Linux 2.6.27-7-generic x86_64
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev video

[Apport retracing service (apport)]

StacktraceTop:?? ()

[Pedro Villavicencio (pedro)]

Thanks for your bug report. Please try to obtain a backtrace http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the bug report. This will greatly help us in tracking down your problem.

[Martin Gerdzhev (mgerdjev)]

Actually I haven't experienced this problem for a long time now. I believe it got fixed with some update and I cannot obtain a backtrace.

[Nicolas Valcarcel (nvalcarcel)]

Same problem here.

[Luis Díaz (piponazo)]

I have the same problem in Ubuntu Jaunty 9.04 (Alpha5).

[Huygens (huygens-25)]

Like Luis, I have the problem too with Jaunty alpha5 64bit.

[Lafa (luis-alves)]

Same problem here, running latest jaunty 5/Mar/2009 on 64 bits

[Christofer Bergman (morindhal)]

I also have this problem on Ubuntu 9.04 Alpha 5 x86-64 ..

Crashes very often and makes my whole system lag before that, I have only experienced this in Firefox but that may be simply because I use that browser more often than the others.

[Shane Fagan (shanepatrickfagan)]

Also effects me.

[Mauricio (darthsteel)]

Same problem here!

2009/3/8 shane fagan <email address hidden>

> Also effects me.
>
> --
> npviewer.bin crashed with SIGSEGV
> https://bugs.launchpad.net/bugs/282323
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>

--
KDE RULES :)

www.linuxuruguay.org

[Tchalvak (tchalvak)]

So the question is, is there something specific that we can do to help diagnose this frequently occurring bug.

[Shane Fagan (shanepatrickfagan)]

No the question is:
Is this a problem with Nvidia or Ubuntu.

[Simon Ruggier (simon80)]

On Mon, Mar 9, 2009 at 10:56 AM, shane fagan <email address hidden> wrote:
> No the question is:
> Is this a problem with Nvidia or Ubuntu.

I don't know if it's intentional, but your email has an obnoxious tone
to it, and you provide no reason why you think this is somehow Nvidia
specific. Nevertheless, this problem is either with nspluginwrapper,
or Adobe Flash. If it has any relation to video drivers (which it may
not), then it's not specific to Nvidia, seeing as how I have ATI
hardware and still experience it.

Also, to various other people, please avoid commenting that you too
are affected by the bug, it wastes all subscribers' time, and doesn't
help the bug get solved. It is already abundantly clear this bug
affects many people, and there's a link at the top you can click on if
you really must express that it affects you too.

[Shane Fagan (shanepatrickfagan)]

I was just being blunt sorry.

[electhor (electhor)]

The auto crash detector informed me of this fault following an update, otherwise I would not have known it had occurred. I am using jaunty alpha 5, 64bit.

[Timothy Wilson (timothy-gbcwhittier)]

jaunty alpha 5, 64bit, clicked the updater in the top bar when the updater window was already open.

[Kraemer (djkraemer)]

The same bug gets me too. Jauntuy alpha 6 x64.

[bwallum (rbw2)]

+1 AMD64 Jaunty Latest at 16/03/09. Apport report submitted I think. Where do they go?

[Tchalvak (tchalvak)]

I believe that apport files don't get attached unless you create the bug report as a new bug, at which point it automatically attaches all the relevant files.

More to the point, my experience with reporting any bugs here on launchpad is:
Report bug with information.
Someone comes along and asks you to do a backtrace on a bug crash that already occurred.
Someone then comes along and marks the bug as invalid for lacking information.

Conclusion:
According to the bug maintainers, there's essentially no point in apport bug reporting unless you jump through the complicated hoops of doing a backtrace as well. https://wiki.ubuntu.com/Backtrace
As far as I can tell, no-one even makes use of posted apport bug information, they always request Backtraces, implying that even if you have apport report a bug... ...you would then have to make that crash reoccur -while actively running a backtrace program- before anyone is going to even look at it.

[electhor (electhor)]

Crash recurred after updates on 20/03/09. Had not occurred since the last report on 11/03/09. Januty alpha 6, 64bit.

[LaChild (shafer-w2002)]

Ok since I use the Flash player all day long as part of my job, I attempted to get the backtrace requested. This is my first ever backtrace so please tell me if I did anything wrong...

I waited until I saw this from gdb
-------------------------------------------------------------------
Program received signal SIGSEGV, Segmentation fault.
------------------------------------------------------------------------

Then I ran the following right after
------------------------------------------------------------------------
(gdb) backtrace full
(gdb) info registers
(gdb) thread apply all backtrace
(gdb) quit
------------------------------------------------------------------------

Thread apply all backtrace replied:
------------------------------------------------------------------------
Cannot find new threads: generic error
------------------------------------------------------------------------

The file is attached below.

Hope it helps, and if I did it wrong please let me know what I did wrong and I'll try to grab it again

PS. This is an to-date copy of Janty Alpha6 AMD64 as of 1:53 am Central

[Tchalvak (tchalvak)]

A backtrace was made and attached, please advise if it is correctly done and provides sufficient information.

[Tchalvak (tchalvak)]

LaChild, I'm going to assume that you were using flash in firefox at the time that you did the backtrace.

[LaChild (shafer-w2002)]

That's correct. One thing to note about this issue is that flash never seems to stop working when this happens. I also seem to get the notification about the crash when I move from a page that has flash to one that doesn't. This segfault happened when I moved from one page with flash to another one with flash so no crash icon showed up in the notification area. Could it be because flash spawns a new thread for the new page as seen here or did I just not do it right?

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xf728a750 (LWP 12273)]

[Youri (i-bis)]

Got the same problem with npviewer on Jaunty jackalope Beta 1

[mightymouse2045 (eagleeyes426)]

Same error here - rebooting to see if that sorts it out as I just installed it - but not looking hopeful at this point considering all the people with the same problem above

[CTenorman (ctenorman)]

Same problem here on Jaunty Beta 1.

[cazacugmihai (cazacugmihai)]

Same problem here on Karmic

[wolux (noar78)]

+1 Karmic amd64

[Shane Fagan (shanepatrickfagan)]

Well you could use the 64bit version of adobe flash. It has a few glitches but it works and doesnt crash as much as the 32bit version in the repo. You can get it here http://labs.adobe.com/downloads/flashplayer10.html

[bwallum (rbw2)]

I'm using the 64 bit native flash player as shane fagan suggests on an AMD64 rig running Karmic (25th Sep 09). It is very stable for me.

I downloaded the libflashplayer-10.0.32.18.linux-x86_64.so.tar.gz file from http://labs.adobe.com/downloads/flashplayer10.html.
I placed the extracted libflashplayer.so file into /usr/lib/mozilla/plugins/
I removed nspluginwrapper using synaptic.
and then rebooted (looks very messy if you don't reboot)

[gerstrong (gerstrong)]

I can confirm that!

[Bruce Heerssen (bheerssen)]

Problem still exists in Karmic x86_64, though it seems only some flash videos trigger the crash. Videos from Comedy Central crash every time.

[iMac (imac-netstatz)]

The consistent failure after reaching some videos led me to believe initially that this might be DNS related, but I now realized what is actually happening is the npviewer crash. I would agree that it seems to trip on certain videos every time _ with so many variants of quality and meta_information embedded, I would guess the plugin is not well suited to some formats

Jan 24 14:17:50 laptop kernel: [ 9347.546152] npviewer.bin[4617]: segfault at ff999ed8 ip 00000000ff999ed8 sp 00000000ffe288bc error 14
Jan 24 23:17:56 laptop kernel: [ 5997.051880] npviewer.bin[16934]: segfault at 13 ip 00000000f65fee57 sp 00000000ffdad344 error 4 in libflashplayer.so[f5f22000+993000]

I probably would have not realized I had this issue, however as my son approaches two, there has been an dramatic increase in requests to see "Garbage Trucks" and other animals/machines on you tube after we read books.. and the delay this bug causes during show-time leads to unnecessary mashing of the keyboard as my son mimics my repeated clicking of the mouse.

[dino99 (9d9)]

This version is outdated and no more supported