http://bugs.winehq.org/show_bug.cgi?id=59450 --- Comment #39 from Henri Verbeet <hverbeet@gmail.com> --- (In reply to Tony Fabris from comment #37)
Okay, so who do I report the bug to, then? :-)
It's a philosophical question at this point: Is the bug the handling of the MVK_CONFIG_SYNCHRONOUS_QUEUE_SUBMITS flag, or the actual queue submit code itself?
If it's indeed the issue we think it is, this would be something to report to upstream MoltenVK. The CrossOver build may make the issue easier to encounter, but it exists in upstream MoltenVK as well.
So, reiterating the philosophical question another way: If the bug only repros in mainline MoltenVK when the user changes that flag, then is that even a bug, or is it just user error?
I think that's still a bug. It may not be a very important one if the position of upstream MoltenVK is that synchronous submission is always preferable on current versions of macOS, but in that case it could also be argued that the right thing to do is to simply remove the asynchronous submission code because it's broken.
I haven't tried to compile the mainline MoltenVK code. It took me quite a long time (and tons of help from you) to be able to compile VKD3D at all, and I'm not sure I'm ready to begin that same process for MoltenVK.
Because you gave me a simple and perfect one-line workaround (just force the flag to 1 with a console command), the whole thing has become entirely academic to me now. I'm sure that the folks working on Crossover and/or MoltenVK would love to have the exact bug found and reported, and so that would be my incentive to keep digging. But for me personally, the bug is solidly fixed by that one-liner, and so I no longer actually need anything else. Still, I want to help if I can, and I want to know who report the bug to, if possible.
I can probably write a MoltenVK patch for you to test, but that would still require you to build MoltenVK yourself. I could instead try to make a MoltenVK build for you to test, but the only macOS setup I have available for that purpose is a few versions newer than yours; it may not work. -- 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.