firefox-3.5 crashed with SIGSEGV in __tls_get_addr()

[brentpieczynski]

Binary package hint: firefox-3.5

This difference between this and #339499 is that I'm using firefox-3.5 instead of 3.1, which is what's likely to list this as a new-bug. The bug was caused when I went from the homepage to another location which was <http://www.yahoo.com>, this starting of the Browser then going from the homepage to this other location might trigger, the same behavior.

ProblemType: Crash
Architecture: amd64
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/lib/firefox-3.5b4pre/firefox-3.5
NonfreeKernelModules: nvidia
Package: firefox-3.5 3.5~b4~hg20090330r24021+nobinonly-0ubuntu1
ProcCmdline: /usr/lib/firefox-3.5b4pre/firefox-3.5
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: firefox-3.5
StacktraceTop:
 ?? () from /lib/libc.so.6
 ?? () from /lib/libc.so.6
 ?? () from /lib64/ld-linux-x86-64.so.2
 __tls_get_addr () from /lib64/ld-linux-x86-64.so.2
 ?? () from /lib/libselinux.so.1
Title: firefox-3.5 crashed with SIGSEGV in __tls_get_addr()
Uname: Linux 2.6.28-11-generic x86_64
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev video

[Apport retracing service (apport)]

StacktraceTop:ptmalloc_init () at arena.c:346
memalign_hook_ini (alignment=139706226832160,
?? ()
?? ()
?? () from /lib/libselinux.so.1

[Jonathan Thomas (echidnaman)]

Thank you taking the time to report this bug and helping to make Ubuntu better. However, processing the crash report to get detailed information for the developers failed as the retracer did not generate a useful symbolic stack trace.
Please try to obtain a backtrace manually 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.

[Monkey (monkey-libre)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comment. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!