Using caffe freezes system

[TheRealPingWin]

I'm trying to run overwatch 2 and heard that only caffe can run it without crashes at the moment.
However when I launch battle net from bottles and caffe 7.18 is the selected runner my whole system freezes.
I've tried different runners and only caffe does this. I've tried running older caffe versions but got the same result.
I installed bottles with flatpak and downloaded caffe from there and also tried using lutris but same result.
When I ran journalctl -f | grep --line-buffered kde I got this message:
Oct 05 14:06:02 adamPC plasmashell[962]: file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/Task.qml:385: Unable to assign [undefined] to QString

Also on the lutris discord server I've heard from other arch based system users the same issue, but no one could solve it.

My system and hardware info:
Kernel: 5.15.65-1-MANJARO
Desktop: KDE Plasma v: 5.25.5
Intel Core i5-9600K
Nvidia gtx 1080, driver 515.65.01
Xorg x11
32gb ram

[Kid0h]

I'm having this problem too.
This seems to be a thing with the, it's filling to 100% and the system starts crashing.

My system:
OS: Ubuntu 22.04.1 LTS x86_64
Kernel: 5.17.9-xanmod1
DE: GNOME
WM: Mutter
CPU: Intel i7-8700 (12) @ 4.600GHz
GPU: NVIDIA GeForce GTX 1070
Memory: 4109MiB / 32042MiB

EDIT: On Bottles my ram starts filling up to 100% and on Lutris all my CPU cores spike to 100% usage.

[theochita]

I'm having the same issue.

It spawns hundreds of winedbg processes and pins my cpu at 100%

Same behavior on both bottle and lutris.

OS: Manjaro x86_64
Kernel: 5.19.13-1
DE: GNOME
WM: Mutter
CPU: AMD Ryzen 3900X
GPU: NVIDIA GeForce GTX 3080
Memory: 32GiB

[TheRealPingWin]

I'm in a discord chat group and someone managed to get past the freezing issue and launch battle net, however ov2 still doesn't launch. He said that he gets page error or something like that.
I'm just about to try his advice and I'll update the post.
He mirrored the wine-tkg-git from here: https://github.com/Frogging-Family/wine-tkg-git
then changed the customization.cfg with the caffe one: https://github.com/bottlesdevs/wine/releases/tag/caffe-7.18 but changing _proton_fs_hack="true" to false, then ran ./non-makepkg-build.sh selected default and pasted it to the lutris/bottles runners and used that.

edit: Sadly this wine config doesn't work... can run launcher but no games.

[Tellus]

Aye, that was me.

I've attached stderr output from running the current caffe 7.18 release on my system (Manjaro/Intel/Nvidia): bottles.error.txt

The error doesn't occur if caffe is built without _proton_fs_hack but the build doesn't run Overwatch (or Diablo 3).

I'm not familiar with debugging Wine, so I'm not sure how to go about trying to get a callstack/trace or state for when the regular caffe 7.18 build starts spawning explorer.exe all over the place.

EDIT: I should clarify the "freeze".

With caffe-7.18 (and any build with _proton_fs_hack="true", it seems), wine starts spawning explorer.exe processes until the system runs out of memory and the memkiller (or user) starts killing wine processes to stabilize. The log I attached was from starting wine and killing it after a few moments. I found some older threads around the 'net that suggests clearing the wineprefix if that happens, but that didn't work here.

A tl;dr of stuff I've tried so far:

• caffe-7.18: spawns tonnes of explorer.exe, nothing else happens.
• caffe-7.18 without _proton_fs_hack: Battle.net starts, 3D applications crash with a page fault.
• clearing/recreating wineprefixes have had no effect.
• Bottles/Lutris yields the same result.
• Both the stable v7.18 tag and latest Git version yield the same result.

[Tk-Glitch]

While enabling _proton_fs_hack will still be an issue on affected machines (this is still being investigated - Frogging-Family/wine-tkg-git#874), the regression causing OW2 to not work on wine 7.14+ is now fixed in -tkg builds (the fix is pending upstream - https://gitlab.winehq.org/wine/wine/-/merge_requests/1152). If need be, we offer nightlies here for anyone who'd like to test the fix out.