npviewer.bin crashed with SIGSEGV

Bug #436034 reported by Tim Casey
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nspluginwrapper (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: nspluginwrapper

I had 2 tabs open in firefox. The first was a standard web page with a few flash ads. The second had just finished streaming a flash video (it happened just as I came out of full screen mode).

Description: Ubuntu karmic (development branch)
Release: 9.10

nspluginwrapper:
  Installed: 1.2.2-0ubuntu6
  Candidate: 1.2.2-0ubuntu6
  Version table:
 *** 1.2.2-0ubuntu6 0
        500 http://au.archive.ubuntu.com karmic/multiverse Packages
        100 /var/lib/dpkg/status

firefox:
  Installed: 3.5.3+build1+nobinonly-0ubuntu2
  Candidate: 3.5.3+build1+nobinonly-0ubuntu2
  Version table:
 *** 3.5.3+build1+nobinonly-0ubuntu2 0
        500 http://au.archive.ubuntu.com karmic/main Packages
        100 /var/lib/dpkg/status

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
Date: Fri Sep 25 02:25:49 2009
Disassembly: 0xff99cd48: Cannot access memory at address 0xff99cd48
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/lib/nspluginwrapper/i386/linux/npviewer.bin
Package: nspluginwrapper 1.2.2-0ubuntu6
ProcCmdline: /usr/lib/nspluginwrapper/i386/linux/npviewer.bin --plugin /usr/lib/flashplugin-installer/libflashplayer.so --connection /org/wrapper/NSPlugins/libflashplayer.so/10235-3
ProcEnviron:
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-10.35-generic
SegvAnalysis:
 Segfault happened at: 0xff99cd48: Cannot access memory at address 0xff99cd48
 PC (0xff99cd48) not located in a known VMA region (needed executable region)!
SegvReason: executing unknown VMA
Signal: 11
SourcePackage: nspluginwrapper
StacktraceTop:
 ?? ()
 ?? () from /usr/lib/flashplugin-installer/libflashplayer.so
 ?? () from /usr/lib/flashplugin-installer/libflashplayer.so
 ?? () from /usr/lib/flashplugin-installer/libflashplayer.so
 ?? () from /usr/lib/flashplugin-installer/libflashplayer.so
Title: npviewer.bin crashed with SIGSEGV
Uname: Linux 2.6.31-10-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Tim Casey (tjcasey) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:?? ()
?? ()
?? ()
?? ()
?? ()

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
Changed in nspluginwrapper (Ubuntu):
status: New → Invalid
Revision history for this message
Apport retracing service (apport) wrote : Crash report cannot be processed

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate an useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

libgcc1: installed version 1:4.4.1-4ubuntu1, latest version: 1:4.4.1-4ubuntu3
gcc-4.4-base: installed version 4.4.1-4ubuntu1, latest version: 4.4.1-4ubuntu3
libstdc++6: installed version 4.4.1-4ubuntu1, latest version: 4.4.1-4ubuntu3
lib32stdc++6: installed version 4.4.1-4ubuntu1, latest version: 4.4.1-4ubuntu3
python2.6: installed version 2.6.2-0ubuntu6, latest version: 2.6.2-3ubuntu1
libcups2: installed version 1.4.1-1, latest version: 1.4.1-2
python2.6-minimal: installed version 2.6.2-0ubuntu6, latest version: 2.6.2-3ubuntu1
lib32gcc1: installed version 1:4.4.1-4ubuntu1, latest version: 1:4.4.1-4ubuntu3
libpython2.6: installed version 2.6.2-0ubuntu6, latest version: 2.6.2-3ubuntu1

Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!

tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.