[FEISTY] firefox crashed [@sem_wait@GLIBC_2.0] [@?? -- libflashplayer.so]

Bug #114279 reported by Marco Meoni
2
Affects Status Importance Assigned to Milestone
firefox (Ubuntu)
Invalid
Undecided
Mozilla Bugs

Bug Description

Binary package hint: firefox

[apport] firefox-bin crashed with SIGSEGV in __kernel_vsyscall()

ProblemType: Crash
Architecture: i386
Date: Sat May 12 17:41:18 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/lib/firefox/firefox-bin
Package: firefox 2.0.0.3+1-0ubuntu2
PackageArchitecture: i386
ProcCmdline: /usr/lib/firefox/firefox-bin
ProcCwd: /home/sbaush
ProcEnviron:
 SHELL=/bin/bash
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=it_IT.UTF-8
Signal: 11
SourcePackage: firefox
StacktraceTop:
 __kernel_vsyscall ()
 raise () from /lib/tls/i686/cmov/libpthread.so.0
 ?? ()
 ?? ()
 ?? ()
Uname: Linux sbaush-laptop 2.6.20-15-generic #2 SMP Sun Apr 15 07:36:31 UTC 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

Tags: mt-confirm
Revision history for this message
Marco Meoni (marcomeoni) wrote :
Revision history for this message
Hilario J. Montoliu (hjmf) (hmontoliu) wrote : Retraced Stacktrace

Retrace done.

Extract from retraced stacktrace:
...
#3 <signal handler called>
#4 sem_wait@GLIBC_2.0 () from /lib/tls/i686/cmov/libpthread.so.0
#5 ?? () from /usr/lib/flashplugin-nonfree/libflashplayer.so
#6 start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#7 clone () from /lib/tls/i686/cmov/libc.so.6
...

Tagging as mt-confirm for further processing

Changed in firefox:
assignee: nobody → mozilla-bugs
importance: Undecided → High
status: Unconfirmed → Needs Info
Revision history for this message
Hilario J. Montoliu (hjmf) (hmontoliu) wrote : Retraced Thread Stacktrace

Retraced Thread Stacktrace

Revision history for this message
Hilario J. Montoliu (hjmf) (hmontoliu) wrote :

Thank you Marco for your report.

Can you indicate how did it happen? Is the crash reproducible?
Please, describe which extensions/plugins do you have enabled.

Thanks

Revision history for this message
Alexander Sack (asac) wrote :

Unfortunately, your crash report does not contain the information that we need in order to process this bug properly. This regularly happens and is not the reporters fault.

If you ever manage to capture another crash report, don't hesitate to open a *new* bug. Thanks for your contribution,

 - Alexander

Changed in firefox:
importance: High → Undecided
status: Needs Info → Rejected
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.