http://bugs.winehq.org/show_bug.cgi?id=59450 --- Comment #36 from Henri Verbeet <hverbeet@gmail.com> --- (In reply to Tony Fabris from comment #35)
And since, before I knew about that variable, the hang bug repro'd without that variable being set at all, I wonder if that means (as I discussed in my prior comment) that the value is defaulting to 0 on my system, even though my system is higher than version 10.14, so it should have defaulted to 1?
Not necessarily. The CrossOver sources unfortunately don't contain the scripts used to control MoltenVK compilation, but the defaults for configuration variables like MVK_CONFIG_SYNCHRONOUS_QUEUE_SUBMITS can be changed at build time. I.e., building MoltenVK with $ make MVK_CONFIG_SYNCHRONOUS_QUEUE_SUBMITS=0 would make it default to 0.
I don't think it's the fault of the folks at https://github.com/KhronosGroup/MoltenVK in this case, because their version on GitHub just hard-codes that variable's default value to 1 without any version check.
From a quick look at the upstream MoltenVK sources, I think it has the same synchronisation issue, even though it may require setting MVK_CONFIG_SYNCHRONOUS_QUEUE_SUBMITS=0 to trigger it.
-- 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.