[Bug 47731] World of Warcraft BFA Crash with error 132 Memory could not be read.

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=47731

--- Comment #28 from Sveinar Søpler <cybermax at dexter.no> ---
(In reply to krovikan from comment #27)
> Always that I exit of the game, I have a 132 error.
> 
> I am with a wine-staging 5.8.

Same for me.
I am actually struggling with the difference of nVidia driver "branches".

Did some tests with nVidia "Vulkan beta - 440.66.1x" versions, and those seems
to crash with "Error #132" rather randomly while playing, vs. the 440.100 and
450.51 Beta seems to crash mostly just when logging out after you have played
for 2-3+ hours. Just logging in/out does not crash for me, but raiding a couple
of hours, switching characters+++ for a few hours, exiting the game always
generates a #132 crash.

This is with wine-lutris-4.16 + dxvk 1.4.6. (Does not really matter what
wine/dxvk version i have used tho.. #132 happens in varying degree anyway)

I have only used this driver for 3 or 4 days, so it is too early to say if it
NEVER crashes mid-game, but i am seriously getting ticked off by this. Since
this CLEARLY (atleast on my system) exhibits differences when switching between
nVidia driver branches/versions, i do believe this is something that is not
necessarily wine and/or dxvk to blame.

For me this kind of crash usually only happens when i have played for a few
hours without logging out. This in turn COULD mean some sort of memory
management issue perhaps? Not something easily tested, as you cannot just
change a setting, and log on do a quick M+ and think "Wow.. problem solved.. i
did not crash".
It is more of "How many crashes did i have this week per hour played, vs last
week when i used X or Y".

-- 
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.