1315699 - Attempting to load tab with video causes content tab spinner to be displayed and nothing else - GPU process & Media GPU Process Decoding interaction

Status: RESOLVED FIXED

(Core :: Graphics, defect, P3)

Description

[Ryan Jones-Ward [:sciguyryan]]

Attachment: about:support information

This issue appears to be related to the enabling of the content GPU process.

Attempting to load a page with a video (noted originally on Youtube) causes the page to load and render to a point, then revert a white tab with nothing but the tab spinner present. Attempting to reload the page does not achieve anything and this issue appears to be completely repeatable.

Disabling the GPU process via layers.gpu-process.dev.enabled and restarting the browser appears to completely resolve the issue.

I have attached the contents of the about:support tab and a screenshot (not that there is much to show!) as separate attachments on this bug.

If I can provide any further information please let me know. Given the nature of the issue I am unsure what additional information would be useful here.

Comment 1

[Ryan Jones-Ward [:sciguyryan]]

Attachment: Tab Spinner on Blank Tab

Comment 2

[Ryan Jones-Ward [:sciguyryan]]

After doing a little more research it seems to be an interaction between media.gpu-process-decoder being enabled and layers.gpu-process.dev.enabled being enabled.

As such I will leave this to someone else to figure out which component it should be filed against. Disabling either of these resolves the issue - enabling both causes it to reoccur.

Comment 3

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

No immediate ideas yet from me - Ryan, did you enable the media.gpu-process-decoder pref by hand?

Comment 4

[Ryan Jones-Ward [:sciguyryan]]

(In reply to David Anderson [:dvander] from comment #3)
> No immediate ideas yet from me - Ryan, did you enable the
> media.gpu-process-decoder pref by hand?

Yes, I did enable it by hand for testing a while back.

Comment 5

[Ryan Jones-Ward [:sciguyryan]]

This still appears to be an issue in the latest nightly - I have just retested it this morning.

Do we have any further information regarding what is going on here?

Comment 6

[Ryan Jones-Ward [:sciguyryan]]

This appears to have been resolved by the patch landed in bug 1318083.