Critical: Invalid Frame Time Spikes in v2.4 After Extended Runtime

[DevTechProfile]

In the latest v2.4 release, invalid frame times are observed after several minutes of runtime. Specifically, the MsBetweenPresent and MsBetweenDisplayChange metrics intermittently spikes to extremely high values (≥1000 ms).

These spikes occur sporadically, approximately 5 out of 1000 frames, but their magnitude is severe enough to significantly distort low-percentile performance metrics (e.g., 1% / 0.1% lows). As a result, benchmark outputs become unreliable and potentially misleading.

This issue has been reported independently by multiple users, indicating it is not an isolated case. Given that the current CapFrameX beta was rolled out with v2.4, I am considering withdrawing the beta release until this issue is resolved.

Reproducible after ~10 minutes of runtime and tabbing between the game and Windows or another app. Example data see attached csv files.

Observed on:
NVIDIA GPUs
Intel GPUs
AMD GPUs: not yet tested

These are the console arguments that are used in CapFrameX:
.\PresentMon-2.4.0-x64.exe --restart_as_admin --stop_existing_session --no_track_input --qpc_time_ms --track_pc_latency

Valid_Frame_1.csv

Invalid_Frame_1.csv

[DevTechProfile]

I've reworked PresentMon's ETW buffer management and added status monitoring to CapFrameX. Looking good so far.

[RodroG-85]

Hello @DevTechProfile . So, is this fixed on the development build #73?

[DevTechProfile]

Currently testing... and still a memory leak striking in.

[RodroG-85]

Thank you for the update @DevTechProfile . I hope you find a workaround, and the PresentMon team also looks into this.

[DevTechProfile]

I've fixed it, will create a PR.

[DevTechProfile]

Here is the PR: #560

After some in-depth testing I can confirm that the memory leak issue has been fixed.