migrations/egui
1
0
Fork 0
mirror of https://github.com/emilk/egui.git synced 2026-06-26 22:53:14 -04:00
Code Activity

Free textures after submitting queue instead of before with wgpu renderer (#5226)

Browse Source 
* Closes #5224

I'm unfamiliar with wgpu, so I'd like someone to confirm, that calling
`wgpu::Texture` _after_ `wgpu::Queue::submit` is in fact the right thing
to do.

---------

Co-authored-by: Andreas Reich <r_andreas2@web.de>
This commit is contained in:
Rusty-Cube
2024-10-06 20:50:10 +02:00
committed by GitHub
parent 0f2b427ff4
commit 7bd6f83f18
1 changed files with 10 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

17
crates/egui-wgpu/src/winit.rs
View File

@@ -668,13 +668,6 @@ impl Painter {
);
}
{
let mut renderer = render_state.renderer.write();
for id in &textures_delta.free {
renderer.free_texture(id);
}
}
let encoded = {
crate::profile_scope!("CommandEncoder::finish");
encoder.finish()
@@ -691,6 +684,16 @@ impl Painter {
vsync_sec += start.elapsed().as_secs_f32();
};
// Free textures marked for destruction **after** queue submit since they might still be used in the current frame.
// Calling `wgpu::Texture::destroy` on a texture that is still in use would invalidate the command buffer(s) it is used in.
// However, once we called `wgpu::Queue::submit`, it is up for wgpu to determine how long the underlying gpu resource has to live.
{
let mut renderer = render_state.renderer.write();
for id in &textures_delta.free {
renderer.free_texture(id);
}
}
let screenshot = if capture {
self.screen_capture_state
.as_ref()