Bug 166866 – Measure how common it is for content to deal with WebGL context loss

• Status: RESOLVED
• Resolution: FIXED
• Component: Canvas

[Chris Dumez]

Measure how common it is for content to deal with WebGL context loss.

[Chris Dumez]

<rdar://problem/29883469>

[Chris Dumez]

Created attachment 298403 [details]
WIP Patch

[Chris Dumez]

Created attachment 299614 [details]
Patch

[Chris Dumez]

<rdar://problem/30171195>

[Chris Dumez]

Created attachment 299616 [details]
Patch

[Build Bot]

Comment on attachment 299616 [details]
Patch

Attachment 299616 [details] did not pass mac-debug-ews (mac):
Output: http://webkit-queues.webkit.org/results/2942573

New failing tests:
media/modern-media-controls/tracks-support/tracks-support-show-panel-fullscreen.html

[Build Bot]

Created attachment 299628 [details]
Archive of layout-test-results from ews113 for mac-elcapitan

The attached test failures were seen while running run-webkit-tests on the mac-debug-ews.
Bot: ews113  Port: mac-elcapitan  Platform: Mac OS X 10.11.6

[Alex Christensen]

Comment on attachment 299616 [details]
Patch

r=me
Should we also measure how often a contextLoss handler would have been called if it were present/is called if it is present?

[Chris Dumez]

(In reply to comment #8)
> Comment on attachment 299616 [details]
> Patch
> 
> r=me
> Should we also measure how often a contextLoss handler would have been
> called if it were present/is called if it is present?

I don't think this is important at the moment. What we want to know is would it be safe for us to take away / restore the WebGL context and rely on the pages dealing with context loss via those event handlers.

[WebKit Commit Bot]

Comment on attachment 299616 [details]
Patch

Clearing flags on attachment: 299616

Committed r211151: <http://trac.webkit.org/changeset/211151>

[WebKit Commit Bot]

All reviewed patches have been landed.  Closing bug.