FS#41322 - [firefox] crash, again

Attached to Project: Arch Linux
Opened by mattia (nTia89) - Thursday, 24 July 2014, 08:45 GMT
Last edited by Jan de Groot (JGC) - Tuesday, 05 August 2014, 12:38 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan de Groot (JGC)
Ionut Biru (wonder)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:

firefox crash on certain website
e.g. gmail

this time I get a message in dmesg:

[ 1760.085396] Chrome_ChildThr[8450]: segfault at 0 ip 00007fc1aa7083d3 sp 00007fc1970c1500 error 6 in libmozalloc.so[7fc1aa707000+2000]


Additional info:
* firefox-31.0-1


Steps to reproduce:

open gmail go to inbox, wait the crash
(usually it happens 1 second after the page is entirely loaded)
This task depends upon

Closed by  Jan de Groot (JGC)
Tuesday, 05 August 2014, 12:38 GMT
Reason for closing:  Fixed
Additional comments about closing:  Fixed with gstreamer/vaapi updates.
Comment by Doug Newgard (Scimmia) - Thursday, 24 July 2014, 13:08 GMT
Is gst-vaapi installed? If so, try uninstalling it.
Comment by mattia (nTia89) - Thursday, 24 July 2014, 13:16 GMT
yes, it's installed.

I tryied uninstalling that but I get the same results

both gst-vaapi and gstreamer0.10-vaapi
Comment by patrick (potomac) - Thursday, 24 July 2014, 13:50 GMT
I don't have this bug when I go to gmail website,

maybe it's a faulty firefox extension ( like flashblock or adblock ) or a plugin who triggers this bug,

you can test again by disabling the firefox extensions,

a better test is to create a new firefox profile and see after if the bug is still here
Comment by mattia (nTia89) - Thursday, 24 July 2014, 14:06 GMT
I created a new profile. Without do anything else, I go to gmail then I login and after 10 seconds firefox crashes
Comment by mattia (nTia89) - Monday, 28 July 2014, 15:29 GMT
apparently with latest update (gstreamer and other stuff) I don't have this issue anymore

In my honest opinion this bug is solved!

Loading...