1375449 - Crash in mozalloc_abort | NS_DebugBreak | mozilla::ipc::FatalError | mozilla::dom::ContentChild::FatalErrorIfNotUsingGPUProcess | libxul.so@0xe31014 | libxul.so@0x10c31d1 | mozilla::layers::TextureClient::InitIPDLActor

Status: RESOLVED WONTFIX

(Core :: Graphics: Layers, defect, P3)

Description

[Simona Badau, Desktop QA]

Attachment: about:support

This bug was filed from the Socorro interface and is 
report bp-f7ad4084-ebf1-4850-a227-6bdfb0170622.
=============================================================
Mozilla/5.0 (X11; Linux x86_64; rv:56.0) Gecko/20100101 Firefox/56.0
Build ID: 20170621172513 

Reproduced this issue using a dirty profile, I can provide it, if needed (I will attach the about:support section).

STR:
1. Launched Firefox
2. Beside the already pinned tabs (9 pinned tabs) opened 9 more tabs (CNN, BBC, Facebook, NYTimes, about:crashes and 4 crash reports from Soccoro)
3. Crashed Nightly twice using the crash me now add-on (https://addons.mozilla.org/en-US/firefox/addon/crash-me-now-simple/?src=ss)
4. After the restart - restored the pages
5. Navigate really fast from one tab to the other until there is no spinning sign left in any tab

Expected results:
Step 5: the content of the pages should load properly.

Actual results:
Step 5: The content of the pages is white and Nightly becomes unresponsive. Killed Nightly and after the restart, the following crash reports were generated.

https://crash-stats.mozilla.com/report/index/42713a00-db97-4a0a-bc7a-54a760170622
https://crash-stats.mozilla.com/report/index/a0b50be6-b631-40b9-b228-e53a30170622
https://crash-stats.mozilla.com/report/index/f7ad4084-ebf1-4850-a227-6bdfb0170622
https://crash-stats.mozilla.com/report/index/72a5ab14-4167-466c-b94b-0770b0170622

https://crash-stats.mozilla.com/report/index/65bf94f5-ea9c-41cc-9ecd-330550170622

Comment 1

[Simona Badau, Desktop QA]

Following the steps from the Description, I also got a crash on Firefox 54, that is very similar with the already mentioned signatures:
https://crash-stats.mozilla.com/report/index/0ec5bd64-ed2f-4d2b-8e44-ecf370170622

Comment 2

[Dzmitry Malyshau [:kvark]]

The symptoms and the code involved looks heavily related to bug 1316632: https://bugzilla.mozilla.org/show_bug.cgi?id=1316632#c33
David, could that be the case that the submitted fix didn't cover this scenario?

Comment 3

[David Anderson [:dvander] - inactive, e-mail if emergency]

I can't really tell what is going on in those crash reports. It looks like the IPC channel to the compositor is dead. But if the GPU process isn't enabled (it is disabled on Linux), the compositor bridge should never be shut down without the whole process going down.

Comment 4

[Sylvestre Ledru [:Sylvestre]]

Closing because no crash reported since 12 weeks.