totem-plugin-viewer crashed with SIGSEGV while playing embedded audio in firefox

[vanDrunen]

Binary package hint: totem

Totem-plugin-viewer crashes when playing embedded audio from www.nederland.fm in firefox 3.0.13

ProblemType: Crash
Architecture: amd64
Date: Fri Aug 7 21:08:00 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/lib/totem/totem-plugin-viewer
NonfreeKernelModules: nvidia
Package: totem 2.27.2-0ubuntu2
ProcCmdline: /usr/lib/totem/totem-plugin-viewer --plugin-type gmp --user-agent Mozilla/5.0\ (X11;\ U;\ Linux\ x86_64;\ en-US;\ rv:1.9.0.13)\ Gecko/2009080311\ Ubuntu/9.10\ (karmic)\ Firefox/3.0.13 --mimetype video/x-msvideo --statusbar
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-5.24-generic
SegvAnalysis:
 Segfault happened at: 0x411af0: mov 0x8(%rax),%rcx
 PC (0x00411af0) ok
 source "0x8(%rax)" (0x00000008) not located in a known VMA region (needed readable region)!
 destination "%rcx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: totem
Stacktrace: #0 0x0000000000411af0 in ?? ()
StacktraceTop: ?? ()
Title: totem-plugin-viewer crashed with SIGSEGV
Uname: Linux 2.6.31-5-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin mythtv plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:totem_embedded_play (emb=0x1766400,
nanosleep () from /lib/libpthread.so.0
IA__g_usleep (microseconds=<value optimized out>)
gst_xvimagesink_event_thread (xvimagesink=0x1a97d00)
g_thread_create_proxy (data=0x1ab2360)

[Linus Sjögren (thelinx-deactivatedaccount-deactivatedaccount-deactivatedaccount-deactivatedaccount-deactivatedaccount)]

Not just affecting Firefox, happened for me in Chrome too.

[Pedro Villavicencio (pedro)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Is this reproducible with Lucid? Please test and provide us of feedback about it, Thanks in advance.

[Pedro Villavicencio (pedro)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.