Summary: | webgl/2.0.0/conformance/extensions/angle-instanced-arrays.html is failing | ||
---|---|---|---|
Product: | WebKit | Reporter: | Alexey Proskuryakov <ap> |
Component: | WebGL | Assignee: | Nobody <webkit-unassigned> |
Status: | NEW --- | ||
Severity: | Normal | CC: | dino, gman, justin_fan, kbr, kkinnunen, kpiddington, oconnorct1, webkit-bug-importer |
Priority: | P2 | Keywords: | InRadar |
Version: | WebKit Local Build | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
See Also: | https://bugs.webkit.org/show_bug.cgi?id=205483 |
Description
Alexey Proskuryakov
2019-12-31 14:28:24 PST
The failure reproduces on Catalina WK2, Mac mini 8,1, but not on iMac Pro. I'm on MacOS Monterey 12.3 (21E230) MacBook Pro (15-inch, 2017) Radeon Pro 560 4 GB Intel HD Graphics 630 1536 MB WebGL2 works ok, but I build a line algorithm that relies on gl.drawArraysInstanced With WebGL1 it has ok performance, on WebGL2 the frame rate drops below 10. I don't have this issue with Firefox or Chrome. For some reason Chrome uses Radeon Pro 560 4 GB, and Firefox uses Intel HD Graphics 630 1536 MB. They both work fine. I can't get Safari to report back the GPU using 'WEBGL_debug_renderer_info' so I have no clue which Safari is using. Is there a way to give you a better report to see what the potential problem is? I'm worried a lot of people are going to get poor FPS from Safari, so I am sticking with WebGL1 with ANGLE_instanced_arrays extension if Safari is in use for now (although it's still bad performance comparatively to other browsers). MrMartian: could you please provide a test case showing the performance problem you're facing? It would probably be better to file a separate bug about that rather than including it on this one, which is about a specific correctness test failure. We'd generally seen that ANGLE's Metal backend has eliminated mysterious performance problems seen with the OpenGL backend - so if you find this isn't the case, we'd like to investigate it. Thanks. |