mirror of
https://github.com/wolfpld/tracy.git
synced 2026-07-23 22:49:14 +00:00
D3D11_QUERY_DATA_TIMESTAMP_DISJOINT can report Frequency == 0 even when Disjoint == FALSE. Neither the initial CPU/GPU calibration loop nor the per-frame Collect() path guarded against this, so `timestamp * (1000000000 / disjoint.Frequency)` divides by zero and crashes the profiled application with EXCEPTION_INT_DIVIDE_BY_ZERO inside client instrumentation code. Treats a zero frequency the same as an existing guard already does for a disjoint result: skip/retry in calibration, and in Collect() advance the checkpoint and drop the batch via TracyD3D11Panic, matching the existing disjoint-timestamp handling immediately above it.