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

Capturing too much? #16

Open
greggman opened this issue Nov 3, 2022 · 1 comment
Open

Capturing too much? #16

greggman opened this issue Nov 3, 2022 · 1 comment

Comments

@greggman
Copy link
Collaborator

greggman commented Nov 3, 2022

So I added a Resource view. At the top of the "Steps" pane, click "Resources". It shows all the objects (textures, buffers, etc...)

It's saving too much. I guess if capture is not on we can discard any canvas textures and after a frame or so discard any command buffers that have been submitted?

@Kangz
Copy link
Collaborator

Kangz commented Nov 3, 2022

Textures have a "state" that can be "destroyed" if they are a canvas texture that has been presented. The UI could filter them out maybe? (and we could add the same for command buffers etc). However it seems hard to know exactly what resources to capture or not on beginTrace because textures may be referenced in bind groups that are referenced in commands etc. So I don't know that we can remove these from the trace.

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

2 participants