'The trace file, filename.rmv, failed to load.'

[fares-soliman]

I am trying to capture a memory trace of the Mesh Node Workgraph sample using RMV that comes with the latest Developer Tool suite (RMV version 1.13.0.5).
I click 'Dump Trace' and the rmv file is created without issue, However, when trying to open it, I am greeted with the error message 'The trace file, MeshNodeSample_DX12.rmv, failed to load.'

After downloading the source, building, and running, I get the same error but I can see that two asserts fail:

RMT_ASSERT(out_resource_update->resource_type == kRmtResourceTypeBuffer);

out_resource_update->resource_type here is actually of type kRmtResourceTypeImage

and

RMT_ASSERT(out_timeline->series_memory_buffer)

out_timeline->series_memory_buffer is NULL because the code before attempted to allocate a ludicrously large chunk of memory, its either a garbage value or its calculation involved a loop that went on for too long

Have I done something incorrectly? Thanks in advance

OS: Windows 11 Pro
OS Description: 26100.1.amd64fre.ge_release.240331-1435
GPU: AMD Radeon RX 7600
Driver Packaging Version: 25.10.25.01-250724a-417878C-AMD-Software-Adrenalin-Edition
Driver Software Version: 25.8.1
RMV commit hash: 29bb28f
Mesh Node Workgraph sample commit hash: f3486b1dd8eee1f0dd7f4410ac9d22f9a6c31ea7

EDIT: Typo + clarification

[ahosier]

Hi fares-soliman,

Thank you for reporting this issue. If possible, could you attach the RMV trace file that isn't loading to this ticket and we'll take a look.

Thanks,
Tony.

[fares-soliman]

Sure, sorry for the late reply. This machine I access to right now is slightly different than the original ticket, but the issue persists

Here are the differences in my previous specs, the rest are the same:

OS: Windows 10 Education
OS Description: 19041.1.amd64fre.vb_release.191206-1406
Driver Packaging Version:25.10.25.10-250825a-418637C-AMD-Software-Adrenalin-Edition
Driver Software Version: 25.9.1

MeshNodeSample_DX12D.zip

[ahosier]

There seems to be an earlier assert where an invalid token is being processed (kRmtTokenTypeReserved1) in RmtParserAdvance(). Could you please try and take another capture and see if that fixes things? Sometimes we see traces that get corrupt every now and again. If it's repeatable on your end, we'll try and duplicate the issue with as near to your system config as we can. I have a capture here from an RX 9070 that looks fine.

Thanks,
Tony.

[fares-soliman]

Yes this will happen every time, I have created multiple captures of the mesh node sample and none of them can open