multi-draw broken after the recent update to Safari. (Safari 15.4 (17613.1.17.1.6))

56 views
Skip to first unread message

Philip Taylor

unread,
Mar 21, 2022, 10:31:45 AMMar 21
to webgl-d...@googlegroups.com
Hello, after the recent update to Safari 15.4 (17613.1.17.1.6), our multi-draw code started throwing exceptions on all multi-draw calls. (multiDrawElementsWEBGL)

WebGL: INVALID_OPERATION: multiDrawElementsWEBGL: countsOffset out of bounds

We haven't been able to address the issue, and have since disabled multiDraw on Safari, but this is now causing a performance regression that we would like to avoid.

Can I be guided by an expert in this area to find a solution? There is a possibility that we are doing something wrong on our side, but so far we can't get to the bottom of it.

Thanks
--
Zea Homepage
Philip TAYLOR
CTO, Zea Inc.
Montréal, Québec

The contents of this e-mail are confidential with all rights reserved to the author. It is illegal to use or divulge this information without authorization. If you have received this e-mail by mistake, please notify me immediately by replying to the e-mail. 

David Smith

unread,
Mar 22, 2022, 3:22:38 PMMar 22
to webgl-d...@googlegroups.com
Try turning off antialiasing. This fixed a number of issues for me.

David A. Smith

Twitter: @GoCroquet
Skype: inventthefuture

I am a part of all that I have met; 
Yet all experience is an arch wherethro' 
Gleams that untravell'd world whose margin fades 
For ever and forever when I move. 


--
You received this message because you are subscribed to the Google Groups "WebGL Dev List" group.
To unsubscribe from this group and stop receiving emails from it, send an email to webgl-dev-lis...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/webgl-dev-list/CAC7g9xQ%2BWpRO0h7fbKxjfeHORVn6-r_UazZpuNNVDjUpLSuEKA%40mail.gmail.com.

Ken Russell

unread,
Mar 22, 2022, 8:02:29 PMMar 22
to WebGL Dev List
Hi Philip,

Unfortunately a bug was introduced in Safari's validation for WEBGL_multi_draw along with what looks like a security bug fix.

I've posted a patch to WebKit fixing it in https://bugs.webkit.org/show_bug.cgi?id=238239 . Unfortunately it will probably take some time for this to propagate out.

Sorry that a regression like this made it past automated testing of any browser. There are safeguards in place to prevent this sort of thing from happening, but it looks like there are some gaps in WebGL conformance testing in WebKit.

In the interim - I'd encourage you and other developers to test your products regularly with pre-release versions of browsers like Chrome Canary / Dev, Firefox Nightly, Microsoft Edge Canary Channel, and Safari Technology Preview, and file any bugs against browsers as soon as you see them.

Thanks,

-Ken



Philip Taylor

unread,
Mar 23, 2022, 3:27:44 PMMar 23
to webgl-d...@googlegroups.com
Thanks a lot for this feedback Ken. 

We will try to make an effort to implement testing of the beta browsers going forward so we can catch these issues earlier.

Phil


Zea Homepage
Philip TAYLOR
CTO, Zea Inc.

Reply all
Reply to author
Forward
0 new messages