http://bugs.winehq.org/show_bug.cgi?id=59450 --- Comment #12 from Tony Fabris <tfabris@gmail.com> --- Okay interesting. I reproduced a hang with those messages active in the d3d12_command_list_ResourceBarrier function. And the last is not at the start of the function. If these messages are to be believed, it's not hanging *inside* that function. The last six lines of the output are: vkd3d:0130:fixme:d3d12_command_list_ResourceBarrier ****** START d3d12_command_list_ResourceBarrier ****** vkd3d:0130:fixme:d3d12_command_list_ResourceBarrier ****** END d3d12_command_list_ResourceBarrier ****** vkd3d:0130:fixme:d3d12_command_list_ResourceBarrier ****** START d3d12_command_list_ResourceBarrier ****** vkd3d:0130:fixme:d3d12_command_list_ResourceBarrier ****** END d3d12_command_list_ResourceBarrier ****** vkd3d:0130:fixme:d3d12_command_list_ResourceBarrier ****** START d3d12_command_list_ResourceBarrier ****** vkd3d:0130:fixme:d3d12_command_list_ResourceBarrier ****** END d3d12_command_list_ResourceBarrier ****** -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.