firefox crashed with SIGSEGV @nsNavHistory::SetPageTitleInternal

Bug #292332 reported by Jesse Zbikowski
6
Affects Status Importance Assigned to Milestone
firefox-3.0 (Ubuntu)
Triaged
Medium
Unassigned

Bug Description

Binary package hint: firefox-3.0

This is an automatically generated bug report from Kubuntu Intrepid.

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/lib/firefox-3.0.3/firefox
NonfreeKernelModules: nvidia
Package: firefox-3.0 3.0.3+nobinonly-0ubuntu2
ProcAttrCurrent: unconfined
ProcCmdline: /usr/lib/firefox-3.0.3/firefox
ProcEnviron:
 LANGUAGE=en_US
 PATH=/home/username/bin:/home/username/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: firefox-3.0
StacktraceTop:
 ?? ()
 ?? () from /usr/lib/xulrunner-1.9.0.3/libxul.so
 ?? () from /usr/lib/xulrunner-1.9.0.3/libxul.so
 ?? () from /usr/lib/xulrunner-1.9.0.3/libxul.so
 ?? () from /usr/lib/xulrunner-1.9.0.3/libxul.so
Title: firefox crashed with SIGSEGV
Uname: Linux 2.6.27-7-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner vde2-net video

Tags: apport-crash
Revision history for this message
Jesse Zbikowski (embeddedlinuxguy) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:?? ()
nsNavHistory::SetPageTitleInternal (this=0x95f1cb8, aURI=0xb053170, aTitle=@0xb02b31c)
nsNavHistory::CommitLazyMessages (this=0x95f1cb8) at nsNavHistory.cpp:4872
nsTimerImpl::Fire (this=0x9d8b8a0) at nsTimerImpl.cpp:400
nsTimerEvent::Run (this=0xadfc0da8) at nsTimerImpl.cpp:490

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Alexander Sack (asac) wrote : Re: firefox crashed with SIGSEGV

Hi,

unfortunately your crash report didn't yield the required information. This can eventually happen. Please go ahead and submit new crash reports in future.

Thanks for your contribution,
  - Alexander

Changed in firefox-3.0:
status: New → Invalid
Revision history for this message
Alexander Sack (asac) wrote :

sorry ... that was wrong ... its a good one i think.

Changed in firefox-3.0:
importance: Undecided → Medium
status: Invalid → Triaged
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.