[Bug 47198] League of Legends 9.10 Crash after champ select

[wine-bugs at winehq.org]

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

--- Comment #29 from mail+wine at m-reimer.de ---
For me it's also not 100% stable.

I can start the game client and I can play all game modes.

But from time to time (often after one game completely finished and I want to
join a second one) I get the crashes again.

In this case I have to get sure that *all* wine processes are gone. If I
restart League after that, I can rejoin the game where I was thrown out by the
crash.

This is OK and better than no solution at all. I'm not a that regular League
player and TBH I just keep loosing my lanes :P


Would be interesting to get some deeper insight into this issue. Why does using
"seccomp" have any impact here? Is this just an attempt to block some stuff
that is done by League?

Why is this "memory expansion" needed? Just to store some info? Would it be
possible to just malloc the right amount of memory and then store the pointer
to this memory into the pthread struct memory?

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