Implement EXT_disjoint_timer_query_webgl2
Categories
(Core :: Graphics: CanvasWebGL, enhancement, P3)
Tracking
()
People
(Reporter: fs, Unassigned)
References
(Blocks 1 open bug, )
Details
(Keywords: dev-doc-needed, Whiteboard: [gfx-noted])
Comment 1•8 years ago
|
||
Updated•6 years ago
|
Updated•6 years ago
|
Updated•6 years ago
|
What would be needed to implement this in Firefox? Alternatively, is there a way to profile WebGL2 shader execution in Firefox without this extension?
Comment 3•3 years ago
|
||
This extension is required to get GPU timings. We still have code that handles this, we just need to re-audit it for security concerns before we can re-enabled it in a post-spectre world.
In the interim, would it be possible to have an about:config setting that enables it? I suspect the primary usecase for GPU timing information is local profiling during development. This would at least match the behavior of the .reduceTimerPrecision. category of flags.
Having a single browser that can get accurate CPU and GPU timings would be invaluable during development.
Comment 5•3 years ago
•
|
||
You should be able to try it if you enable webgl.enable-privileged-extensions, though this is unsafe for the general web.
Note that Firefox does not have a different EXT_disjoint_timer_query_webgl2, and uses EXT_disjoint_timer_query for both webgl1 and webgl2.
(In reply to Jeff Gilbert [:jgilbert] from comment #5)
You should be able to try it if you enable webgl.enable-privileged-extensions, though this is unsafe for the general web.
Note that Firefox does not have a different EXT_disjoint_timer_query_webgl2, and uses EXT_disjoint_timer_query for both webgl1 and webgl2.
That's super helpful; thanks! I had tried webgl.enable-privileged-extensions but didn't know to use EXT_disjoint_timer_query.
Updated•2 years ago
|
Updated•7 months ago
|
Updated•7 months ago
|
Description
•