firefox-bin crashed with SIGSEGV

[AmonSacha]

Binary package hint: firefox

1. Using 10.04 Lucid (Beta 1)
2. Package is 3.6.3+nobinonly-0ubuntu1
3. Expected to be able to browse the internet.
4. Firefox crashes seemingly whenever the wind is blowing in the wrong direction. No rhyme or reason to when or why it crashes as far as I can see.

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: firefox 3.6.3+nobinonly-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-16.25-generic
Uname: Linux 2.6.32-16-generic i686
NonfreeKernelModules: nvidia
Architecture: i386
CrashCounter: 1
Date: Mon Apr 5 16:12:39 2010
ExecutablePath: /usr/lib/firefox-3.6.3/firefox-bin
FirefoxPackages:
 firefox 3.6.3+nobinonly-0ubuntu1
 firefox-gnome-support 3.6.3+nobinonly-0ubuntu1
 firefox-branding 3.6.3+nobinonly-0ubuntu1
 abroswer N/A
 abrowser-branding N/A
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100318)
ProcCmdline: /usr/lib/firefox-3.6.3/firefox-bin
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
Signal: 11
SourcePackage: firefox
StacktraceTop:
 ?? () from /usr/lib/firefox-3.6.3/libxul.so
 ?? () from /usr/lib/firefox-3.6.3/libxul.so
 ?? () from /usr/lib/firefox-3.6.3/libxul.so
 ?? () from /usr/lib/firefox-3.6.3/libxul.so
 ?? () from /usr/lib/firefox-3.6.3/libxul.so
Title: firefox-bin crashed with SIGSEGV
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
SegvAnalysis:
 Segfault happened at: 0x48a422 <__kernel_vsyscall+2>: ret
 PC (0x0048a422) ok
 destination "(%esp)" (0xbf86b8fc) ok
 SP (0xbf86b8fc) ok
 Reason could not be automatically determined. (Unhandled exception in kernel code?)
SegvReason: Reason could not be automatically determined. (Unhandled exception in kernel code?)

[Apport retracing service (apport)]

StacktraceTop:
 ReleaseData (data=0x1d9cf2c, flags=1) at nsSubstring.cpp:113
 nsAString_internal::Finalize (this=0xac9b8d14)
 nsDependentSubstring::Rebind (this=0xac9b8d14,
 nsScannerSubstring::AsString (this=0xac9b8cfc)
 CNavDTD::CollectAttributes (this=0xac1f1b40,

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Paul White (paulw2u)]

Reporter no longer uses Launchpad
Although bug confirmed, crash may have been for different reason
No activity on report by reporter for over six years
Closing by marking "Invalid" as cause of crash not established