You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description
When creating and immediately dropping Buffers with mapped_at_creation: true, they don't seem to properly get cleaned up resulting in a memory leak.
Repro steps
Run the following program and observe an ever increasing amount of memory being used.
Expected vs observed behavior
I would expect process memory usage to stay steady given all of the Buffers are immediately freed.
Platform
Tested on Windows 10 with Vulkan (default) and DX12 backend using wgpu, wgpu-core, and wgpu-hal version 0.19.3 and against trunk (as shown with the Git reference in the Cargo.toml above).
The text was updated successfully, but these errors were encountered:
Description
When creating and immediately dropping
Buffer
s withmapped_at_creation: true
, they don't seem to properly get cleaned up resulting in a memory leak.Repro steps
Run the following program and observe an ever increasing amount of memory being used.
Ideally, a runnable example we can check out.
Expected vs observed behavior
I would expect process memory usage to stay steady given all of the
Buffer
s are immediately freed.Platform
Tested on Windows 10 with Vulkan (default) and DX12 backend using
wgpu
,wgpu-core
, andwgpu-hal
version0.19.3
and against trunk (as shown with the Git reference in theCargo.toml
above).The text was updated successfully, but these errors were encountered: