question about memory_tracker layers about agi HOT 4 CLOSED

Hi @official-minister, apologies for the delay.

The memory tracker in core/memory_tracker/ is an optimization to reduce the size of our graphics traces. As there is some bad interactions with perfetto trace processor, it might be disabled in some cases.

Now, you may refer to core/vulkan/vk_memory_tracker_layer/ : this is a vulkan layer prototype that has severe limitations, and we disabled it altogether. We are currently exploring alternative ways to track graphics memory.

from agi.

I find bugs in perfetto and propose a issue. Maybe you can provide a error trace file for them:
google/perfetto#34

from agi.

Thanks for the pointer to the perfetto issue. We need to clarify a few things to precisely understand what's going on:

1. Which version do you use to capture the trace? (GAPID or AGI, and which commit?)

2. On which device do you capture the trace, with which GPU driver version?

3. Which AGI/GAPID version do you use to open the trace? (GAPID or AGI, and which commit?)

4. Can you share the gapis coredump that you get, or any kind of stack trace?

5. Can you share the perfetto trace? (You can attach it to a github message. If github refuse to upload it, you can try to zip it and upload the zip version).

from agi.

@official-minister this bug's been stuck waiting to get more information for a few months so we are proceeding to close it now. If you can provide more information as requested by @hevrard , please re-open it and we'll take action. I recommend you try the latest developer release of AGI which contains lots of fixes since your bug was originally reported. Thank you!!

from agi.