969258 - e10s crash in mozilla::layers::CompositableParentManager::ReceiveCompositableUpdate(mozilla::layers::CompositableOperation const&, std::vector<mozilla::layers::EditReply, std::allocator<mozilla::layers::EditReply> >&)

Status: RESOLVED WORKSFORME

(Core :: Graphics: Layers, defect)

Description

[Trevor Rowbotham [:rowbot]]

This crash seems to only happen when I have browser.tabs.remote preference set to true.  The browser crashes constantly whenever I open menus or navigate using the back and forward buttons or pretty much anything.  I can't reproduce this crash with only OMTC enabled.  Could this possibly be related to having new textures enabled (bug 957560) whenever OMTC is enabled on Windows?


Adapter Description	NVIDIA GeForce GTX 470
Adapter Drivers	nvd3dumx,nvwgf2umx,nvwgf2umx nvd3dum,nvwgf2um,nvwgf2um
Adapter RAM	1280
Device ID	0x06cd
Direct2D Enabled	true
DirectWrite Enabled	true (6.2.9200.16571)
Driver Date	1-15-2014
Driver Version	9.18.13.3467
GPU #2 Active	false
GPU Accelerated Windows	1/1 Direct3D 11 (OMTC)
Vendor ID	0x10de
WebGL Renderer	Google Inc. -- ANGLE (NVIDIA GeForce GTX 470 Direct3D9Ex vs_3_0 ps_3_0)
windowLayerManagerRemote	true
AzureCanvasBackend	direct2d
AzureContentBackend	direct2d
AzureFallbackCanvasBackend	cairo
AzureSkiaAccelerated	0

Comment 1

[Liz Henry (:lizzard)]

Trevor, thanks for reporting this. 

Ioana, can someone on your team help try to reproduce this crash? Thanks!

Comment 2

[Trevor Rowbotham [:rowbot]]

FWIW, I can no longer reproduce this crash.  I had originally suspected bug 957560 as the cause of this, and I see that a patch landed in that bug 4 days after I reported this crash.  That patch may have fixed this crash, but I was never able to confirm that bug 957560 was the actual cause.

Comment 3

[Bogdan Maris, Desktop Test Engineering]

I tried to reproduce the crash on three different machines with different GPU`s (AMD Radeon HD 6450, NVIDIA GeForce 210, Intel HD 2000) both on nightly build from 2014-02-06 and 2014-03-13. I got only one crash on nightly build from 2014-02-06 (bp-074ff007-be2a-4ec7-8258-5ffdb2140313) which I was not able to reproduce. No crashes whatsoever on latest Nightly.

I used various scenarios that people commented in crash reports of this signature. 
https://crash-stats.mozilla.com/report/list?signature=mozilla%3A%3Alayers%3A%3ACompositableParentManager%3A%3AReceiveCompositableUpdate%28mozilla%3A%3Alayers%3A%3ACompositableOperation+const%26%2C+std%3A%3Avector%3Cmozilla%3A%3Alayers%3A%3AEditReply%2C+std%3A%3Aallocator%3Cmozilla%3A%3Alayers%3A%3AEditReply%3E+%3E%26%29&product=Firefox&query_type=contains&range_unit=weeks&process_type=any&version=Firefox%3A27.0.1&hang_type=any&date=2014-03-13+10%3A00%3A00&range_value=3#tab-comments

No crashes were registered in Socorro in the last 3 weeks on latest Nightly and Aurora and based on comment 2 I`m marking this bug as worksforme.
https://crash-stats.mozilla.com/query/?product=Firefox&version=Firefox%3A29.0a2&platform=win&platform=mac&platform=lin&range_value=3&range_unit=weeks&date=03%2F13%2F2014+14%3A00%3A00&query_search=signature&query_type=contains&query=mozilla%3A%3Alayers%3A%3ACompositableParentManager%3A%3AReceiveCompositableUpdate%28mozilla%3A%3Alayers%3A%3ACompositableOperation+const%26%2C+std%3A%3Avector%3Cmozilla%3A%3Alayers%3A%3AEditReply%2C+std%3A%3Aallocator%3Cmozilla%3A%3Alayers%3A%3AEditReply%3E+%3E%26%29&reason=&release_channels=&build_id=&process_type=any&hang_type=any