gfx-rs/wgpu · error
TIMESTAMP_QUERY_INSIDE_PASSES feature must be enabled to cal
Error message
TIMESTAMP_QUERY_INSIDE_PASSES feature must be enabled to call write_timestamp in a render pass.
What it means
Panic from the WebGPU backend's write_timestamp stub on a render pass. The browser API exposes no equivalent of writing a timestamp inside a pass, so the method is intentionally unimplemented and any call aborts immediately.
Source
Thrown at wgpu/src/backend/webgpu.rs:3961
_max_count: u32,
) {
panic!("MESH_SHADER feature must be enabled to call multi_draw_mesh_tasks_indirect_count")
}
fn insert_debug_marker(&mut self, label: &str) {
self.inner.insert_debug_marker(label);
}
fn push_debug_group(&mut self, group_label: &str) {
self.inner.push_debug_group(group_label);
}
fn pop_debug_group(&mut self) {
self.inner.pop_debug_group();
}
fn write_timestamp(&mut self, _query_set: &dispatch::DispatchQuerySet, _query_index: u32) {
panic!("TIMESTAMP_QUERY_INSIDE_PASSES feature must be enabled to call write_timestamp in a render pass.")
}
fn begin_occlusion_query(&mut self, query_index: u32) {
self.inner.begin_occlusion_query(query_index);
}
fn end_occlusion_query(&mut self) {
self.inner.end_occlusion_query();
}
fn begin_pipeline_statistics_query(
&mut self,
_query_set: &dispatch::DispatchQuerySet,
_query_index: u32,
) {
// Removed from WebGPU in https://github.com/gpuweb/gpuweb/pull/2296
}
View on GitHub (pinned to 3e11ff59bf)
Solutions
- Move timestamp writes to the command encoder level if supported
- Skip timestamp queries entirely when running on the WebGPU backend
Defensive patterns
Strategy: validation
When it happens
Trigger: Thrown at wgpu/src/backend/webgpu.rs:3961 when the library encounters an invalid state.
Common situations: See trigger scenarios.
AI-assisted analysis of gfx-rs/wgpu@3e11ff59bf (2026-09-03).
Data as JSON: /api/errors/ef8cbc9437b22dd7.
Report an issue: GitHub.