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

On SteamOS, gpuvis failed to visualize the captured trace file. #80

Open
wenyouyang opened this issue Feb 2, 2023 · 2 comments
Open

Comments

@wenyouyang
Copy link

On SteamOS,

  1. Use the sample scripts at folder ./gpuvis/sample to capture a event trace.
    $ sudo ./trace-cmd-setup.sh
    $ sudo ./trace-cmd-start-tracing.sh
    $ sudo ./trace-cmd-capture.sh
    $ sudo ./trace-cmd-stop-tracing.sh
    Then a file named trace_02-02-2023_13-20-27.dat is created

  2. Use gpuvis application to visualize.
    $ gpuvis trace_02-02-2023_13-20-27.dat

It failed with errors shown as below.
image

[Error] read_header_files: header_page not found.
[Error] read_trace_file: setjmp error called for trace_02-02-2023_13-20-27.dat
[Error] load_trace_file(trace_02-02-2023_13-20-27.dat) failed.

Is there anybody experienced this error?

It is deeply appreciated for any suggestions.

@mikesart
Copy link
Owner

mikesart commented Feb 7, 2023

Hi Wenyou. I think the issue you're running into is the same as this:
#50
And sorry - I'm currently working at another company and just haven't had time to fix this...

@lostgoat
Copy link
Collaborator

lostgoat commented Feb 7, 2023

If you capture a trace on steamdeck via the devkit tool you won't encounter this issue:
https://partner.steamgames.com/doc/steamdeck/loadgames

Once you have the devkit tool connected you can use the 'System Trace' button to capture and copy a gpuvis 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

3 participants