Open arswaw opened 1 month ago
This is surprising, I wonder if there is some undefined behavior... cc @rconde01
I am pursing a similar issue with intel: https://github.com/rconde01/intel_driver_indirect_call_hang
Maybe the example is doing something wrong - I will review, but I don't think so? Or maybe the driver gets cranky in conjunction with other things that chrome is doing behind the scenes? @arswaw if you have the time it would be interesting if you could disable various pieces of the renderer and see what pushes it over the edge?
More broadly, I think perhaps chrome needs to treat these as DOS issues because if it happens too many times Windows will block the GPU from the chrome instance.
Did-you/could-you report to AMD? It may truly be a driver issue.
@rconde01 I apologize that I hadn't addressed your comment sooner. I just reported the driver timeout to AMD.
I have time to look at this. Can you give me suggestions as to what to disable once I download the project locally?
Hey @arswaw. I'm at conference this week but i will try to get back to you next week with some details.
Hi,
On the a-buffer page, there is a driver timeout that occurs with AMD Ryzen 5 5500U on my HP Envy x360 laptop. 15m-eu0033dx
Is this a programming error or is this model of GPU not expected to be able to run the demo?