Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#25661 - [Firefox] 6 segfaults
Attached to Project:
Arch Linux
Opened by Jussi Saarinen (jtts) - Friday, 19 August 2011, 01:46 GMT
Last edited by Jan Alexander Steffens (heftig) - Tuesday, 23 August 2011, 16:40 GMT
Opened by Jussi Saarinen (jtts) - Friday, 19 August 2011, 01:46 GMT
Last edited by Jan Alexander Steffens (heftig) - Tuesday, 23 August 2011, 16:40 GMT
|
DetailsDescription:
Since firefox got upgraded to version 5, firefox has crashed alot. Since then I have made a clean installation of ArchLinux, removed all extensions and plugins and made a clean profile, and none of it seem to help. Additional info: Package version(s): extra/firefox 6.0-1 extra/firefox-i18n-de 6.0-2 extra/firefox-i18n-en-gb 6.0-2 extra/firefox-i18n-fi 6.0-2 extra/firefox-i18n-ja 6.0-2 extra/firefox-i18n-sv-se 6.0-2 Config: Clear new profile, all plugins and addons removed. Backtrace: (gdb) backtrace full #0 0x00007ffff64bd72e in ?? () from /usr/lib/firefox-6.0/libxul.so No symbol table info available. #1 0x0000000000000000 in ?? () No symbol table info available. Steps to reproduce: Start firefox. Browse the Internet until it crashes (usually doesn't take that long). |
This task depends upon
Closed by Jan Alexander Steffens (heftig)
Tuesday, 23 August 2011, 16:40 GMT
Reason for closing: None
Additional comments about closing: Defective hardware.
Tuesday, 23 August 2011, 16:40 GMT
Reason for closing: None
Additional comments about closing: Defective hardware.
You also need to provide a better trace to them.
However, it looks like the segfaults were caused by a broken memory module. So feel free to close this bug.