firefox crashed with SIGSEGV in start_thread()

Bug #442365 reported by Walter_Wittel
40
This bug affects 8 people
Affects Status Importance Assigned to Milestone
firefox-3.5 (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: firefox-3.5

My wife was just surfing on a third? instance of firefox when the system crashed (restarted). I've tried several times since last night to upload the full report and either gotten server timeout errors or client errors starting up firefox, so am just uploading the abreviated report. Let me know if you want the full report (I'll leave it in /var/crash for awhile) and we can figure out how I can upload it. Thanks.

ProblemType: Crash
Architecture: i386
CheckboxSubmission: 10129b34737ccce5dde695974272e29d
CheckboxSystem: efe96daad1e2b8af01b857b891a9a8c8
CrashCounter: 1
Date: Sat Oct 3 22:48:42 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/lib/firefox-3.5.3/firefox
Package: firefox-3.5 3.5.3+build1+nobinonly-0ubuntu3
ProcCmdline: /usr/lib/firefox-3.5.3/firefox
ProcCwd: /home/walter
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-11.38-generic
Signal: 11
SourcePackage: firefox-3.5
StacktraceTop:
 ?? () from /usr/lib/flashplugin-installer/libflashplayer.so
 start_thread () from /lib/tls/i686/cmov/libpthread.so.0
 clone () from /lib/tls/i686/cmov/libc.so.6
Title: firefox crashed with SIGSEGV in start_thread()
Uname: Linux 2.6.31-11-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
SegvAnalysis:
 Segfault happened at: 0x781422 <__kernel_vsyscall+2>: ret
 PC (0x00781422) ok
 destination "(%esp)" (0xa99fbd4c) ok
 Stack memory exhausted (SP below stack segment)
 SP (0xa99fbd4c) ok
 Reason could not be automatically determined. (Unhandled exception in kernel code?)
SegvReason: Reason could not be automatically determined. (Unhandled exception in kernel code?)

Revision history for this message
Walter_Wittel (wittelw) wrote :
Kees Cook (kees)
description: updated
tags: added: stack-exhaustion
Revision history for this message
Walter_Wittel (wittelw) wrote :

This is way old and I have not had continuing crashing. Maybe not worth chasing at this point?

Revision history for this message
dino99 (9d9) wrote :

This version is outdated and no more supported

Changed in firefox-3.5 (Ubuntu):
status: New → Invalid
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.