https://bugs.winehq.org/show_bug.cgi?id=49233
--- Comment #8 from Olivier F. R. Dierick o.dierick@piezo-forte.be --- (In reply to Ker noa from comment #7)
I wouldn't call it a regression. d3d11_device_CreateDeferredContext1 was a stub in 5.9-staging https://github.com/wine-staging/wine-staging/commit/ 0db92c336fcea4c383a150560f1034cd9cf76366 extended that function and now we probably moved on from being slow due to not being multi threaded to a buffer overflow because the implementation is not complete.
Ok, then it's not a regression.
The underlying issue is still incomplete multi-threading so it is justified to keep the issue and change the symptoms accordingly.
I still think that it should be separate bugs.
The low fps issue is a more generic issue that will get fixed when multi-threading gets implemented properly. That's the main reason why multi-threading is needed.
Fixing the crash may not be sufficient to fix the low fps.
The crash is only a temporary issue that will get resolved when the implementation becomes more complete.
There could be more implementation issues while multi-threading gets implemented (crashes, things not working properly). Those should be reported as separate bugs so that we can keep track of them individually without touching the main bug.
Otherwise, this will be a 'multi-threading' metabug with a big mess of multiple issues and metabugs should be avoided when possible.
Also, valid bugs should not be recycled.
Regards.