RESOLVED FIXED 200031
WebGL context creation is broken when using video textures 
https://bugs.webkit.org/show_bug.cgi?id=200031
Summary WebGL context creation is broken when using video textures
Yehonatan Daniv
Reported 2019-07-23 06:20:28 PDT
Created attachment 374680 [details] bug reproduction When creating a webgl context and drawing form video texture a few weird things happen: 1. max active contexts limit is suddenly 8. 2. creating an additional context returns `null`. 3. creating *another* context crashes the tab, and causing a refresh. Seems to be happening on Safari on all platforms. I have created a reproduction of the bug in a simple webgl program that creates context, loads videosm and draws a frame, on every button click. First 8 clicks work fine. 9th click returns `null` (instead of a new recycled context) and causes an error. 10th click crashes the tab, after trying to recycle the same context from before and printing: `WebGL: INVALID_OPERATION: loseContext: context already lost`. Also attaching the error log.
Attachments
bug reproduction (10.27 KB, text/html)
2019-07-23 06:20 PDT, Yehonatan Daniv 		no flags
Details
Crash log (156.32 KB, text/plain)
2019-07-23 06:27 PDT, Yehonatan Daniv 		no flags
Details
Testcase - works for me (4.96 KB, text/html)
2021-06-15 07:59 PDT, Noam Rosenthal 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
Yehonatan Daniv
Comment 1 2019-07-23 06:27:17 PDT
Created attachment 374681 [details] Crash log
Radar WebKit Bug Importer
Comment 2 2019-07-24 13:07:54 PDT
<rdar://problem/53509448>
Yehonatan Daniv
Comment 3 2021-05-24 05:40:34 PDT
Ping, it's almost 2 years now. Any chance someone can take a look?
Noam Rosenthal
Comment 4 2021-06-15 07:59:06 PDT
Created attachment 431439 [details] Testcase - works for me I tried to reproduce it with a refined test-case and things seem to work as expected, maybe something is missing in the test case?
Yehonatan Daniv
Comment 5 2021-06-15 23:39:09 PDT
Thanks Noam! Seems to be fixed in Safari 14.1.1
Note You need to log in before you can comment on or make changes to this bug.