firefox crashed with SIGSEGV in vfprintf()

[miked]

Binary package hint: firefox-3.0

This keeps crashing on me.

ProblemType: Crash
Architecture: i386
Date: Mon Apr 7 16:35:26 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/lib/firefox-3.0b5/firefox
Package: firefox-3.0 3.0~b5+nobinonly-0ubuntu1
PackageArchitecture: i386
ProcCmdline: /usr/lib/firefox-3.0b5/firefox
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: firefox-3.0
StacktraceTop:
 vfprintf () from /lib/tls/i686/cmov/libc.so.6
 vasprintf () from /lib/tls/i686/cmov/libc.so.6
 ?? () from /usr/lib/libvlc.so.0
 ?? ()
 ?? () from /usr/lib/libvlc.so.0
Title: firefox crashed with SIGSEGV in vfprintf()
Uname: Linux 2.6.24-15-generic i686
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse plugdev sambashare scanner tape
SegvAnalysis:
 Segfault happened at: 0xb7cf8246 <vfprintf+134>: movl $0x25,0x4(%esp)
 PC (0xb7cf8246) ok
 source "$0x25" ok
 destination "0x4(%esp)" (0xa55feff8) in non-writable VMA region: 0xa55fe000-0xa55ff000 ---p None
SegvReason: writing VMA None

[miked (miked11)]

Changed security from private to public

[Apport retracing service (apport)]

StacktraceTop:vfprintf () from /lib/tls/i686/cmov/libc.so.6
vasprintf () from /lib/tls/i686/cmov/libc.so.6
QueueMsg (p_this=0xadf69860, i_queue_id=0, i_type=1, psz_module=0xadf2d4fc "main",
__msg_Generic (p_this=0xadf69860, i_queue_id=0, i_type=1, psz_module=0xadf2d4fc "main",
QueueMsg (p_this=0xadf69860, i_queue_id=0, i_type=1, psz_module=0xadf2d4fc "main",

[Thomas Novin (thomasn80)]

Got the same crash when I switched between one radio station to another on www.sr.se ("LYSSNA PÅ WEBBRADIO"). I have mozilla-plugin-vlc.

[Brian Murray (brian-murray)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 192888, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.