gfx-rs/wgpu · error
clear_texture is not yet implemented
Error message
clear_texture is not yet implemented
What it means
A hard 'unimplemented!' panic in the WebGPU backend's CommandEncoder trait impl: the clear_texture entry point of the encoder has no code path at all, so any call to CommandEncoder::clear_texture on the wasm/WebGPU backend panics instead of clearing. It fires purely because of a missing feature in wgpu's browser-targeting backend, not because of anything wrong with the texture or subresource range passed in.
Source
Thrown at wgpu/src/backend/webgpu.rs:3515
let mapped_desc = webgpu_sys::GpuCommandBufferDescriptor::new();
mapped_desc.set_label(&label);
self.inner.finish_with_descriptor(&mapped_desc)
};
WebCommandBuffer {
inner: buffer,
ident: crate::cmp::Identifier::create(),
}
.into()
}
fn clear_texture(
&self,
_texture: &dispatch::DispatchTexture,
_subresource_range: &crate::ImageSubresourceRange,
) {
unimplemented!("clear_texture is not yet implemented");
}
fn clear_buffer(
&self,
buffer: &dispatch::DispatchBuffer,
offset: crate::BufferAddress,
size: Option<crate::BufferAddress>,
) {
let buffer = buffer.as_webgpu();
match size {
Some(size) => {
self.inner
.clear_buffer_with_f64_and_f64(&buffer.inner, offset as f64, size as f64)
}
None => self
.inner
.clear_buffer_with_f64(&buffer.inner, offset as f64),View on GitHub (pinned to 3e11ff59bf)
Solutions
- Clear via a render pass with a clear loadOp instead of clear_texture on the web backend
- Track and skip explicit texture clears when targeting WASM
Defensive patterns
Strategy: fallback
When it happens
Trigger: Thrown at wgpu/src/backend/webgpu.rs:3515 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/25a0cce9771a87f9.
Report an issue: GitHub.