FS#34738 - [firefox] 20.0.1-1 segfaults on some websites

Attached to Project: Arch Linux
Opened by bjornoslav (bjornoslav) - Thursday, 11 April 2013, 22:07 GMT
Last edited by Evangelos Foutras (foutrelis) - Friday, 12 April 2013, 14:32 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan de Groot (JGC)
Ionut Biru (wonder)
Evangelos Foutras (foutrelis)
Jan Alexander Steffens (heftig)
Architecture i686
Severity Critical
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 14
Private No

Details

Description:
Firefox 20.0.1-1 crashes and dumps core on opening some web sites.

Additional info:
* it doesn't matter if the Flash plugin is installed or not, it still crashes.
* https://bbs.archlinux.org/viewtopic.php?id=161341

Steps to reproduce:
* Make sure Firefox version 20.0.1-1 is installed.
* Open www.facebook.com or www.cnn.com/video
* Firefox segfaults.
This task depends upon

Closed by  Evangelos Foutras (foutrelis)
Friday, 12 April 2013, 14:32 GMT
Reason for closing:  Fixed
Additional comments about closing:  firefox 20.0.1-2
Comment by bjornoslav (bjornoslav) - Thursday, 11 April 2013, 22:08 GMT
Also, deleting the profile and starting fresh does not help. The issue remains.
Comment by bjornoslav (bjornoslav) - Thursday, 11 April 2013, 22:19 GMT
I've tested the version downloaded from Mozilla Firefox's web site, it has the same issue. It appears to be an upstream problem.
Comment by Evangelos Foutras (foutrelis) - Thursday, 11 April 2013, 22:40 GMT
Mozilla's build doesn't crash on i686 for me; our own build does.

(Could be a GCC 4.8 related issue since 20.0.1 was the first version built with it.)
Comment by bjornoslav (bjornoslav) - Thursday, 11 April 2013, 23:28 GMT
With JavaScript disabled in preferences, Firefox works properly. Maybe the problem is in the Firefox build itself?
Comment by bjornoslav (bjornoslav) - Thursday, 11 April 2013, 23:43 GMT
A backtrace shows a problem in libxul.so causing stack corruption: https://bbs.archlinux.org/viewtopic.php?pid=1257883#p1257883
Comment by Gerardo Exequiel Pozzi (djgera) - Friday, 12 April 2013, 00:27 GMT
The same thing happens with seamonkey-17-1 (build w/gcc 4.8.0), but seamonkey-2.16.2-1 (build w/gcc 4.7.2) works fine. (at least on i686)
Comment by AndrzejL (AndrzejL) - Friday, 12 April 2013, 03:01 GMT
Confirming the bug. Backtrace: http://pastebin.com/YVtkfHqP

Regards.

Andrzej
Comment by Friedrich Haussmann (haussmann) - Friday, 12 April 2013, 07:27 GMT
Confirming the bug.

SEGFAULT (about 13 out of 15 tests):
1) 'rm -rf ~/.mozilla ~/.macromedia'
2a) 'firefox'
3) open new tab
4) type 'mail.google.com' into the address bar and hit enter
5a) segfault


NO SEGFAULT (100% of the tests):
1)
2b) 'firefox -safe-mode'
3)
4)
5b) page loaded fine
Comment by Arch User (superlex) - Friday, 12 April 2013, 10:07 GMT
I can confirm the problem with firefox 20.0.1 and seamonkey 2.17.
Terminal says "Segmentation fault (core dumped)" and dmesg reports "systemd-journald[117]: File passed too large. Ignoring."
I'm on i686 arch.
Comment by Evangelos Foutras (foutrelis) - Friday, 12 April 2013, 11:24 GMT
Currently rebuilding with GCC 4.7.2 and PGO re-enabled for i686; will be up in a couple of hours.

Loading...