[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 #10 from Zebediah Figura <z.figura12 at gmail.com> ---
(In reply to Sveinar Søpler from comment #9)
> Since you cannot play WoW without staging patches it is kinda hard to say
> this is only a staging bug.

Yes, that's accounted for in the link above.

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

The magic of bisections is that "many hundreds" still only means about ten
steps ;-)

Anyway, yes, it's a lot of work, but someone has to do it, or you have to ask
developers to solve this bug as if they knew nothing about it. Believe me when
I say that's far more difficult.

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