-
Notifications
You must be signed in to change notification settings - Fork 896
-
Notifications
You must be signed in to change notification settings - Fork 896
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
Device capture not working in metal backend #6255
Comments
According to https://developer.apple.com/documentation/xcode/capturing-a-metal-workload-programmatically. I did such modifications in metal's capture implementation and the GPU trace is correctly dumped at the given path.
The destination mush be GpuTraceDocument and the path must be end with the gputrace extension name, or capture will not work.I'm not familiar with the metal so this is just a simple test for reference. |
Are you running inside xcode? The assumption with the existing code is that it was running under xcode. |
no, and I assume this api not required running under xcode. and indeed it should not required running under xcode. I'm using this api to dump metal trace when debug unit test code like this https://github.com/mikialex/rendiation/blob/master/shader/task-graph/src/test.rs. |
Interesting, I didn't know this could work outside of xcode, and have always run inside xcode (even unit tests) that I wanted to capture. We probably need some scheme for communicating a path the user wants to save this under, particularly if they want to save multiple paths. |
Description
The device capture API (
device.start_capture
ordevice.stop_capture
) not working in the metal backend.Repro steps
Place any pair of
device.start_capture
anddevice.stop_capture
between any GPU work doesn't have any effect.Expected vs observed behavior
As the current capture implementation in metal's backend, the metal's GPU capture should be triggered. Maybe the report should be dumped after stop_capture.
Platform
os: macos 14.5, hardware: m2 pro
The text was updated successfully, but these errors were encountered: