https://bugs.winehq.org/show_bug.cgi?id=50800
--- Comment #20 from Henri Verbeet hverbeet@gmail.com --- (In reply to Priit from comment #14)
Are you also using the mesa 21.x?
No, I'm using Mesa 19.0.8. It's possible that makes a difference, yes.
Yes, malloc() only happens after this commit.
That's useful to know.
(In reply to Priit from comment #15)
configure battle.net launcher: Settings > App: On Game Launch: Exit the Battle.net App completely Advanced Features: [ ] (uncheck) Use browser hardware acceleration
Incidentally, "browser hardware acceleration" should work since wine-6.3, but that should be inconsequential for this bug.
(In reply to Priit from comment #19)
Just in case ... how to make the git bisect thing walk back this one commit to last working and build it again, so I don't have to like do all the bisecing thing from the very start? Just to be sure there is no malloc() error?
The easiest thing to do would probably be something like "git checkout -b hs_good 8b3cc57df0b^", which would create a branch "hs_good" at the commit before 8b3cc57df0b, and switch to it. (Likewise, "git checkout -b hs_bad 8b3cc57df0b" would create a branch "hs_bad" at commit 8b3cc57df0b and switch to it.)
It may be worth trying a run WINEDEBUG="warn+heap", to see if that produces more interesting output, although chances are it won't. Somewhat similarly, perhaps a log with WINEDEBUG="+d3d,+d3d11" could provide some insight.