GPU PerfStudio 3.4.19 crashes when loading large api trace

Discussion created by kd-11 on Feb 14, 2016
Latest reply on Feb 19, 2016 by darkradeon

GPUPerfStudio cannot analyze a frame capture when the log file is too large. The capture goes well, but when opening the analysis tools, they all fail in one way or another. API trace gives an error about failing to update and the frame debugger crashes with either "Length cannot be less than zero" or something about wrong string format when casting to a number.

This happens when a lot of draw calls are issued. Unfortunately, this is also when the frame debugger is needed the most for me. The generated log file is about 8.5MB for a frame with ~750 draw calls.

Log attached.


EDIT: I've also added the dot net crash message that is shown if you try to open the frame debugger.