I don't see how this is a vkd3d-proton bug. desc_va is 0 here, so this is obviously going to crash. Seems more like an apitrace issue?
Fair enough, but it still doesn't crash when replaying on native D3D12. Could d3dretrace's behavior be different between native D3D12 on Windows an vkd3d-proton in Wine or does native D3D12 just somehow handle such garbage input?
Full API trace logs would be good. Its likely a resource failed to be mapped or created which re return a null VA for
@Joshua-Ashton d3dretrace.log.gz
Made it extra verbose too, I hope it's not too noisy. Let me know if you need anything else.
Nothing extracted yet.
I'm unable to replay apitrace I've recorded using my Windows VM on
vkd3d-protondue to an error:Unless Wine and/or debug symbols are deceiving me, this would point to this line:
https://github.com/HansKristian-Work/vkd3d-proton/blob/fd05839eb964d0edc0accce6db81d076ad3d33b1/libs/vkd3d/resource.c#L3824
I don't think this is a bug with apitrace because the same trace replays fine in the VM used to record it.
2.6.r144.gfd05839e, built from commit fd05839eb964d0edc0accce6db81d076ad3d33b1Side note, but this apitrace is an attempt to repro AC Valhalla hanging on NV 515, if all goes well it should also hang on replay before I abruptly killed the game to make the trace a bit smaller.