Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consider validating implicitly destroyed texture #3

Open
greggman opened this issue Apr 14, 2024 · 0 comments
Open

Consider validating implicitly destroyed texture #3

greggman opened this issue Apr 14, 2024 · 0 comments

Comments

@greggman
Copy link
Owner

greggman commented Apr 14, 2024

The code currently tracks objects that are destroyed but it can't track canvas textures nor external textures.

A solution, which would be slow, is try to use the texture. Canvas textures require TEXTURE_BINDING iirc. External textures i'm not sure but we could look and implement multiple paths.

For example, if the texture has TEXTURE_BINDING usage then we can bind to a bindGroup and try to reference in a compute shader. WebGPU will emit an error. For external texture we can do similar.

It would be slow-ish so needs an option but it would allow getting the stack from where the command happened.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant