firefox crashed with SIGSEGV

Bug #325425 reported by mcourneyea
8
Affects Status Importance Assigned to Milestone
firefox-3.0 (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: firefox-3.0

hangs then crashes

ProblemType: Crash
Architecture: i386
Date: Wed Feb 4 13:39:28 2009
Disassembly: 0xb7f0f410:
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/lib/firefox-3.0.5/firefox
Package: firefox-3.0 3.0.5+nobinonly-0ubuntu0.8.04.1
PackageArchitecture: i386
ProcCmdline: /usr/lib/firefox-3.0.5/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
Stacktrace: #0 0xb7f0f410 in ?? ()
StacktraceTop: ?? ()
ThreadStacktrace:

Title: firefox crashed with SIGSEGV
Uname: Linux 2.6.24-23-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

Revision history for this message
mcourneyea (courneyea) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:?? ()

Revision history for this message
Chris Coulson (chrisccoulson) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

Changed in firefox-3.0:
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
mcourneyea (courneyea) wrote :

As I said the app hung then crashed, which means that I don't know why it hung and I don't know why it crashed, which means that I don't know how to reproduce it. It's kind of pointless to ask for a backtrace for something I don't know how to do. Sorry. If you can't work with what you've got then I guess it'll have to stay like that.

Revision history for this message
Chris Coulson (chrisccoulson) wrote :

I'll close this bug report for now then, as there isn't enough information to work out what the problem is. I'm sure you'll appreciate that "hangs then crashes" isn't enough information isolate the problem.

If you can recreate the crash and provide a backtrace, or describe the steps to trigger the crash, then please feel free to reopen this bug report.

Thanks

Changed in firefox-3.0:
status: Incomplete → Invalid
Revision history for this message
mcourneyea (courneyea) wrote :

steps to reproduce would have been:

1) open browser
2) navigate internet until app hangs
3) wait for it to crash

...but what you're effectively saying is "works as designed" so we'll leave it there.

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.