https://bugs.winehq.org/show_bug.cgi?id=46218
Sveinar Søpler cybermax@dexter.no changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |cybermax@dexter.no
--- Comment #1 from Sveinar Søpler cybermax@dexter.no --- This is something that only happens for SOME people (or possibly SOME linux distro's.. or SOME kernels) i guess.
I have cleared out the cache MANY times, and never had this issue. Then again, i rarely use regular wined3d dx11, but either using DXVK, or of late i also done some d3d12 w/vkd3d.
I think its kinda hard to troubleshoot this issue, as its not pinpointed to a specific wine version?
Could it be related to kernel? Possibly some starved IO thing in the scheduler perhaps? I've tended to use "deadline" scheduler back when i had a spinning disc for WoW, but lastly i have a nvme drive, and just use "none". Just thinking if it is some sort of data corruption in the files, it could be some weird cache flushing issue submitted from the kernel?
Just suggesting, cos i have used wine with WoW since pre. 2.x, and tend to test git versions of wine and all kinds of weird patches i find for wine and never had that issue. Atm i use wine-tkg-3.21 w/ESYNC patches (same as Lutris uses xept i compile myself).