Skip to content

Timestamps are wrong on Vulkan #84

@Dinnerbone

Description

@Dinnerbone

I'm not sure if this is an issue with this library, the rust tracy bindings, or tracy itself - so I figured I'd just shoot here and see if anyone has a suspicion as to what's wrong.

Checking out the current code and running cargo run --example demo --features tracy whilst having the Tracy profiler open, no valid GPU spans seem to be visible in Tracy. If I force DX12 or GL it works, so it seems to be specific to Vulkan.

With Vulkan I can see some suspicious duration spans reported in the statistics. Nothing on the timeline (but I haven't tried running it for 94 days to see if it'll show up :D)
image

With DX12 they look good and thus are visible on the timeline:
image

(I've tested on both Tracy v10, which is the version in the lockfile, and v11.1 by doing a cargo update)

The chrome flamegraphs seem fine and valid for both, so it's likely something to do with the actual Tracy integration rather than wgpu reporting invalid data. I also think it's unlikely to be Tracy itself or I figure someone would have noticed by now - so my bet is either something wrong with the bindings in rust_tracy_client or the use of the API from this crate.

I've also confirmed this in a real world application using wgpu - the example code is just a useful minimal repro.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions