[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 #9 from Sveinar Søpler <cybermax at dexter.no> ---
(In reply to Zebediah Figura from comment #8)
> This issue seems to have gotten somewhat muddied. And since this keeps
> coming up, I've tried to clarify what we need on a Wiki page:
> <https://wiki.winehq.org/Wine-
> Staging#Reporting_and_debugging_bugs_against_Staging>

Since you cannot play WoW without staging patches it is kinda hard to say this
is only a staging bug.

It is ofc possible to pick those patches that are not just "rebases" when
viewing https://github.com/wine-staging/wine-staging/commits/master

If however a wine upstream patch causes a bug, but you MUST use staging to play
a game, it is a tedious task to bisect ALL patches from 4.14-4.15 as this is
many hundreds and taking quite a few minutes between each compile.. Well..

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