http://bugs.winehq.org/show_bug.cgi?id=59450 --- Comment #20 from Henri Verbeet <hverbeet@gmail.com> --- (In reply to Tony Fabris from comment #19)
Then it runs, and also reproduces the issue. NOTE: I think there might be more than one crash or hang issue. Sometimes I get a crash with a stacktrace on the console, sometimes I get a graphics hang where I can still hear myself make menu selections but the screen doesn't refresh, and those don't have a crash/stacktrace on the console. So that might be two separate bugs. Anyway, attached is the one with the stacktrace. Any ideas on this one?
The interesting part is part is probably entry #5, pointing to libMoltenVK.dylib. I'm not a MoltenVK or Objective-C expert by any stretch, but it looks like Metal is running a "scheduled" handler for a command buffer, added by MoltenVK with MTLCommandBuffer::addScheduledHandler() [1], and the handler then ending up with an "unrecognized selector" exception, possibly because the object the selector is called on was already free'd. The location ("vk_icdGetPhysicalDeviceProcAddr + 117451") just looks wrong. I don't immediately know why that is; perhaps missing/broken debug info. Conveniently though, there's only a single place in MoltenVK that calls addscheduledhandler(): MVKPresentableSwapchainImage::presentCAMetalDrawable() [2]. The "present" selector from the stack trace would be consistent with the "[mtlDrwbl present];" line from presentCAMetalDrawable(). [1] https://developer.apple.com/documentation/metal/mtlcommandbuffer/addschedule... [2] https://github.com/KhronosGroup/MoltenVK/blob/v1.4.1/MoltenVK/MoltenVK/GPUOb... -- 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.