Open EpicureanGit opened 1 year ago
boniek83
commented
1 year ago I have a problem with game not registering input from mouse. From keyboard only ESC key works - nothing else. Tried Proton 8.0-3, Experimental and Hotfix - all the same behaviour. Sometimes it works though and I have no idea why.
Performance is way lower than on Windows - on Linux I'm geting only around 80-90 fps on 6800 xt.
Wemmy0
commented
1 year ago Performance is pretty good for me. I'm at around 144 fps at 1440p with FSR 2.2 and it looks great. (3060ti, 3700x)
Only issues for me:
polluxau
commented
12 months ago
idk why this hasnt been reported yet but using either proton experimental (bleeding edge) or proton 8.0-4 the fps is stuck at 40fps but with proton-ge-8-16 the fps is fine
polluxau
commented
12 months ago
as you can see here the fps is good here with proton-ge
running fedora 39 beta with kde plasma with mesa 23.2.1
boniek83
commented
11 months ago I have a problem with game not registering input from mouse. From keyboard only ESC key works - nothing else. Tried Proton 8.0-3, Experimental and Hotfix - all the same behaviour. Sometimes it works though and I have no idea why.
Performance is way lower than on Windows - on Linux I'm geting only around 80-90 fps on 6800 xt.
Don't have input problem anymore, but performance is still below expectations with stock proton (only about 90-100 fps on 6800xt radv 23.2.1).
foresto
commented
10 months ago Has anyone managed to get valid .webm saved highlights?
I can see the CPU doing work while the video is encoded, but the resulting files are only ~770KiB. They won't play in any player, and mediainfo says they are only 1ms long.
agurenko
commented
10 months ago @foresto it used to work, but I also tried recently and also got 770 kb broken file
boniek83
commented
10 months ago I have a problem with game not registering input from mouse. From keyboard only ESC key works - nothing else. Tried Proton 8.0-3, Experimental and Hotfix - all the same behaviour. Sometimes it works though and I have no idea why. Performance is way lower than on Windows - on Linux I'm geting only around 80-90 fps on 6800 xt.
Don't have input problem anymore, but performance is still below expectations with stock proton (only about 90-100 fps on 6800xt radv 23.2.1).
Performance is within expectations on proton-ge 23 (maybe it worked in earlier versions - didn't test), so that's what I'm using now. I have no more problems.
SopaDeMacaco-UmaDelicia
commented
10 months ago The mouse sens via proton is way off from windows. It's sad that valve doesn't invest in input consistency of games played via proton. Vanilla proton doesn't even support raw imput, my KDE mouse sens impacts in-game sens, which is not right. Proton GE fixes that, but the sens is still off from that on windows.
polluxau
commented
10 months ago The mouse sens via proton is way off from windows. It's sad that valve doesn't invest in input consistency of games played via proton. Vanilla proton doesn't even support raw imput, my KDE mouse sens impacts in-game sens, which is not right. Proton GE fixes that, but the sens is still off from that on windows.
X11 or wayland?
SopaDeMacaco-UmaDelicia
commented
10 months ago The mouse sens via proton is way off from windows. It's sad that valve doesn't invest in input consistency of games played via proton. Vanilla proton doesn't even support raw imput, my KDE mouse sens impacts in-game sens, which is not right. Proton GE fixes that, but the sens is still off from that on windows.
X11 or wayland?
KDE Wayland
polluxau
commented
10 months ago The mouse sens via proton is way off from windows. It's sad that valve doesn't invest in input consistency of games played via proton. Vanilla proton doesn't even support raw imput, my KDE mouse sens impacts in-game sens, which is not right. Proton GE fixes that, but the sens is still off from that on windows.
X11 or wayland?
KDE Wayland
If you try x11 its way better
On kde plasma 6 dev they changed how it works under wayland and its a lot better aswell
SopaDeMacaco-UmaDelicia
commented
10 months ago If you try x11 its way better
On kde plasma 6 dev they changed how it works under wayland and its a lot better aswell
Well, in my opinion games like Overwatch 2 and Apex Legends that support raw mouse input should behave the same everywhere no matter what OS or DE you use. The only way it to be better is to be 1:1 compared to windows with no interference from the system settings. And input inconsistency won't attract FPS enthusiasts to Linux.
polluxau
commented
10 months ago If you try x11 its way better
On kde plasma 6 dev they changed how it works under wayland and its a lot better aswell
Well, in my opinion games like Overwatch 2 and Apex Legends that support raw mouse input should behave the same everywhere no matter what OS or DE you use. The only way it to be better is to be 1:1 compared to windows with no interference from the system settings. And input inconsistency won't attract FPS enthusiasts to Linux.
Yes i agree, i play competitive fps games and i am masters in apex, masters on overwatch
Whenever i want the closest mouse input i use x11 or now im using kde plasma 6 wayland, i can easily keep up with my friends who are gm in overwatch and i got a 4k badge today on the new mouse input under plasma 6 wayland on apex. i guess i prefer mouse input on x11 or kdes new approach for mouse input on wayland under plasma 6
AMDHome
commented
9 months ago Has anyone managed to get valid .webm saved highlights?
I can see the CPU doing work while the video is encoded, but the resulting files are only ~770KiB. They won't play in any player, and mediainfo says they are only 1ms long.
Its an overwatch issue. Not a proton issue. webm doesnt work on windows natively
foresto
commented
9 months ago webm doesnt work on windows natively
In that case, has anyone managed to get valid .mp4 saved highlights?
3DMicks
commented
8 months ago Is the game really supposed to be using 10GB+ of RAM? After the game loads initially, it uses ~5GB but after the "Compiling shaders" step finishes, it sits at least above 11GB of RAM. The game itself is playable (with a performance hit) before this, so I can't imagine it being correct behavior. I vaguely remember this not being an issue a couple of months ago. I tested Proton 8, Experimental, GE and TKG.
INFO: Steam Flatpak Kernel: 6.6.10-arch1-1 DE: KDE Plasma 5.27.10 WM: KWin (Wayland), X11 is the same NVIDIA: 545.29.06
SopaDeMacaco-UmaDelicia
commented
8 months ago Htop shows 4720MB reserved, max settings, FSR2.2 to 4k max quality. Arch, KDE Wayland, Mesa RADV.
3DMicks
commented
8 months ago Here are some screenshots of how it behaves:
Right after loading the game, the game does actually use 5GB, but I forgot to screenshot the exact moment
Compiling Shaders
Finished compiling shaders
In the middle of a match (Suravasa)
After the match
After closing the game, it takes a while for it to fully exit; longer sessions do end up using a little more memory. The game also does this with swap if you don't have enough memory, in this test it used no swap.
Forgot to mention in the last post that I am using __GL_SHADER_DISK_CACHE_SKIP_CLEANUP=1 and an NVIDIA Prime system.
Edit: Just checked, and the env var for skipping cleanup does not make a difference; it still behaves the same with and without it.
Michele1144
commented
8 months ago Is the game really supposed to be using 10GB+ of RAM? After the game loads initially, it uses ~5GB but after the "Compiling shaders" step finishes, it sits at least above 11GB of RAM. The game itself is playable (with a performance hit) before this, so I can't imagine it being correct behavior. I vaguely remember this not being an issue a couple of months ago. I tested Proton 8, Experimental, GE and TKG.
INFO: Steam Flatpak Kernel: 6.6.10-arch1-1 DE: KDE Plasma 5.27.10 WM: KWin (Wayland), X11 is the same NVIDIA: 545.29.06
I have the same issue, using Proton Experimental, Proton-GE and Proton 8. On htop "Overwatch.exe" uses 5 GB when opening the game but then after a couple of minutes it drops even under 10 MB, while the memory is in reality being clogged out (using around 20 GB+ being the only open app, 2 GB used on idle) making the game going 2 FPS and the system totally unstable, with difficulties to close the game too. Right now is unplayable. Also, during the brief time of normal usage, Proton-GE achieves 120 FPS+ with no problems while Proton Experimental and Proton 8 are stuck on 20 FPS with the exact settings.
GPU: NVIDIA GTX 1660 Super with 545.29 driver RAM: 8 GB + 16 GB swap OS: Fedora Workstation 39 using X11 with GNOME 45 Kernel: 6.6.9 Steam RPM
3DMicks
commented
8 months ago Replying to https://github.com/ValveSoftware/Proton/issues/7033#issuecomment-1890753226
I can confirm that I also experience a brief period where it hits high frame rates before plummeting down to around 50% of the expected FPS, not thermal or map-related.
Regarding the 20 FPS I can also confirm that, depending on the Proton version, the game gets locked at around 44–47 FPS for me, with the only fix being to delete the prefix. Switching versions also causes this problem. One way I replicated this issue was to use Experimental/GE and then switch to Proton 8.
Another issue I experience is extremely high CPU usage when moving the mouse if I have a high polling rate. With 1000 Hz I get ~35% less FPS, with 500 Hz ~12% less, and with 250 Hz I see almost no difference.
3DMicks
commented
8 months ago Since "Compiling Shaders" appears for the entire period where the RAM usage increases I tested the game without GPL by using DXVK_CONFIG="dxvk.enableGraphicsPipelineLibrary = False" as an environment variable and the RAM issue was mostly gone. Stutters get predictably worse.
Without GPL, the game starts at around 2.5 GB of RAM and increases after playing some matches to around 4.8 GB. The mouse polling rate issue persists. Since this could be an DXVK issue, I'll try to make an issue on their repo when I can if this isn't Proton/Wine related.
Also, the game's PROTON_LOG=1 are hundreds of megabytes (370 MB at 15 minutes of play) due to a spam that goes like this:
warn:seh:dispatch_exception unknown exception (code=6ba) raised 5 times, then
warn:seh:dispatch_exception EXCEPTION_PRIV_INSTRUCTION exception (code=c0000096) raised once, then
warn:seh:dispatch_exception EXCEPTION_SINGLE_STEP exception (code=80000004) raised ~140k times, then finally
warn:seh:dispatch_exception EXCEPTION_ILLEGAL_INSTRUCTION exception (code=c000001d) raised when I close the game.
Another issue I have is that, sometimes, when the mouse cursor is unlocked (hero selection, pinging, emoting, etc.) the moment it locks again my aim moves all the way up or down, meaning I can't use voice lines in the middle of a fight without the fear of getting completely lost.
3DMicks
commented
8 months ago Replying to https://github.com/ValveSoftware/Proton/issues/7033#issuecomment-1901743831
I just tested GE-Proton 8-27, 25, 20, 15, 10, 5, and TKG, and they all have the same problems. I also tested GE-Proton 7-55, but the game didn't launch because it couldn't detect Steam.
Given how all of these versions have the same issues, I suspect it was probably a game update that causes them.
TerohsLab
commented
7 months ago After the Wine 9 rebalance of Proton Experimental the game looses window focus after a match and you can't regain it. I can load up the game fine, play a game normally and on the play of the game screen the game just looses focus on its own with no way to get it back.
Proton Experimental was working totally fine before the rebase to wine 9.
I feel like we had a similar problem in the past .. maybe a game specific patch got missed in the rebase?
Still works as expected under Proton 8.
Am using the steam version of the game.
kisak-valve
commented
7 months ago Hello @TerohsLab, please add PROTON_LOG=1 %command% to the game's launch options, reproduce the regression, and attach the generated $HOME/steam-$APPID.log to this issue report as a file. (Proton logs compress well if needed.) Also, please copy your system information from Steam (Steam -> Help -> System Information) and put it in a gist, then include a link to the gist in this issue report.
simifor
commented
7 months ago @TerohsLab I played a quickmatch in proton experimental and couldn't reproduce your focus loss issue, does it only happen with specific game modes?
agurenko
commented
7 months ago @TerohsLab I've been playing OW2 with Proton 9 beta and experimental for 4 days now without any difference to previous experimental.
TerohsLab
commented
7 months ago Yeah i can't reproduce it currently. Played 10 quickplay games with logging turned on and it didn't reoccur.
I swear it happened multiple times ( in comp tho ) and through restarts .. and it felt like the same bug that we had before .. the one where would loose window focus on hero death from like 2 years ago.
Hopefully it was just some hickup in Tumbleweed. Once i can nail it down more i will report back.
@kisak-valve https://gist.github.com/TerohsLab/f3a5e1391899eec510909b07a78390fe in case it will become relevant later.
polluxau
commented
7 months ago i see that with the latest proton experimental(bleeding edge) the fps is back to normal on mesa 24 under arch,
let me know if anyone else is also getting normal fps without using proton-ge under an amd card on latest mesa with latest proton experimental(bleeding edge)
TerohsLab
commented
7 months ago Got the crash on camera : [Uploading steam-2357570.zip…]()
TerohsLab
commented
7 months ago TerohsLab
commented
7 months ago Had two more crashes mid comp games. reverting to proton 8 now.
Unless you want specifics .. im out.
simifor
commented
7 months ago @TerohsLab you originally talked about a focus issue, are you talking about a different issue now? and how reproducible were those crashes? were those the first games in a given session? or did you instead play several times before those crashes?
TerohsLab
commented
7 months ago First one was a focus issue, the last 3 straight up crashed the game mid match. I could still hear sound, but graphics froze and i had the force close the game mid comp match.
This happened after having the game open for at least 3-4 hours and many perfectly fine games in comp and open queue.
kisak-valve
commented
6 months ago Overwatch 2 2357570
Issue transferred from https://github.com/ValveSoftware/Proton/issues/7576. @Redhawk18 posted on 2024-03-14T03:40:31:
https://gist.github.com/Redhawk18/bea6a899e6f101597e368fbd54947ae9
Either System freezes or application crashes in game. It seems to happen once every thirty minutes.
This log is 1GB, This was the only way I could upload it steam-2357570.7z.log
@polluxau commented on 2024-03-14T09:02:20:
https://github.com/ValveSoftware/Proton/issues/7033 you can add this log to the already opened issue
simifor
commented
6 months ago @Redhawk18 Have you noticed if the crashes always happen when performing specific actions or being in certain game modes? How many crashes have you encountered? And I see from the logs that you're using proton experimental, have you seen if the crashes still happen on proton 8?
Redhawk18
commented
6 months ago @Redhawk18 Have you noticed if the crashes always happen when performing specific actions or being in certain game modes? How many crashes have you encountered? And I see from the logs that you're using proton experimental, have you seen if the crashes still happen on proton 8?
True be told these crashes have been happening 2021, long before I even used proton. I believe it has something to do with AMD's RDNA1 drivers and I've reached out on their forums and heard nothing back. Historically what would happen is my entire computer would freeze due my graphics card firmware crashing on both Windows and Linux. However more recently Overwatch itself just crashes, not my entire computer. So that's an improvement for sure, but I've never had a smooth time with this game. I'm sure its related to hardware or maybe I just have a lost the silicon lottery with my gpu.
E-D-W-I-N
commented
6 months ago Same freezes, but on Nvidia gpu. Sometimes game just freezes (in game music continues to play) and freezes steam UI (I can't move cursor to Steam window, cursor goes behind it
simifor
commented
6 months ago @E-D-W-I-N in what proton versions? Is this a new behavior? I assume there's some variability, but roughly how long does it take for these to occur? It would also be helpful for you to share your specifications and proton log.
Please add PROTON_LOG=1 %command% to the game's launch options and attach the generated $HOME/steam-$APPID.log to this issue report as a file.
You can retrieve a full system information report by clicking Help > System Information in the Steam client on your machine. Then upload it to Gist
agurenko
commented
6 months ago @E-D-W-I-N in what proton versions? Is this a new behavior? I assume there's some variability, but roughly how long does it take for these to occur? It would also be helpful for you to share your specifications and proton log.
Please add
PROTON_LOG=1 %command%to the game's launch options and attach the generated $HOME/steam-$APPID.log to this issue report as a file. You can retrieve a full system information report by clickingHelp>System Informationin the Steam client on your machine. Then upload it to Gist
It's started to happen for me with a mid-season patch last week. It's usually happens within first 3 games so, around a 30 min mark? Although I had it freeze on a very first match in competetive mode, which tend to be prone to crashes even on windows. I've captured proton log just now, but it's 33 Mb compressed (1.7GiB uncompressed with 20mil lines).
Last lines before the end of the log:
17283.327:0128:0290:trace:unwind:dump_unwind_info unwind info at 000000009E183798 flags 3 prolog 0x4f bytes function 000000009E17F540-000000009E17F93F
17283.327:0128:0290:trace:unwind:dump_unwind_info frame register rbp offset 0x80(%rsp)
17283.327:0128:0290:trace:unwind:dump_unwind_info 0x4f: leaq 0x80(%rsp),rbp
17283.327:0128:0290:trace:unwind:dump_unwind_info 0x47: subq $0x98,%rsp
17283.327:0128:0290:trace:unwind:dump_unwind_info 0x40: pushq %rbx
17283.327:0128:0290:trace:unwind:dump_unwind_info 0x3f: pushq %rdi
17283.327:0128:0290:trace:unwind:dump_unwind_info 0x3e: pushq %rsi
17283.327:0128:0290:trace:unwind:dump_unwind_info 0x3d: pushq %r12
17283.327:0128:0290:trace:unwind:dump_unwind_info 0x3b: pushq %r13
17283.327:0128:0290:trace:unwind:dump_unwind_info 0x39: pushq %r14
17283.327:0128:0290:trace:unwind:dump_unwind_info 0x37: pushq %r15
17283.327:0128:0290:trace:unwind:dump_unwind_info 0x35: pushq %rbp
17283.327:0128:0290:trace:unwind:dump_unwind_info handler 000000009E1714A0 data at 000000009E1837B8
17283.327:0128:0290:trace:unwind:call_unwind_handler calling handler 000000009E1714A0 (rec=00000000179DB5F0, frame=00000000179DB8F0 context=00000000179DAB50, dispatch=00000000179DA2D0)
17283.327:0128:0290:trace:unwind:call_unwind_handler handler 000000009E1714A0 returned 1
17283.327:0128:0290:trace:seh:RtlRestoreContext returning to 000000009E17F813 stack 00000000179DB8F0
17283.330:0128:0290:trace:seh:RtlDeleteFunctionTable 000000009E186000
17288.304:0128:012c:err:sync:RtlpWaitForCriticalSection section 0000000015CC0048 (null) wait timed out in thread 012c, blocked by 0290, retrying (60 sec)
17291.543:0128:0178:err:sync:RtlpWaitForCriticalSection section 0000000015CC0048 (null) wait timed out in thread 0178, blocked by 0290, retrying (60 sec)
17336.028:0150:0154:trace:mscoree:DllMain (00006FFFFC340000, 0, 0000000000000000)
17336.028:0150:0154:trace:loaddll:free_modref Unloaded module L"C:\\windows\\system32\\mscoree.dll" : builtin
17336.028:0150:0154:trace:loaddll:free_modref Unloaded module L"C:\\windows\\system32\\ole32.dll" : builtin
17336.028:0150:0154:trace:loaddll:free_modref Unloaded module L"C:\\windows\\system32\\coml2.dll" : builtin
17336.028:0150:0154:trace:loaddll:free_modref Unloaded module L"C:\\windows\\system32\\combase.dll" : builtin
17336.028:0150:0154:trace:loaddll:free_modref Unloaded module L"C:\\windows\\system32\\rpcrt4.dll" : builtin
17336.028:0150:0154:trace:loaddll:free_modref Unloaded module L"Z:\\mnt\\ssd\\SteamLibrary\\steamapps\\common\\Overwatch\\ErrorReporting\\x64\\dbghelp.dll" : builtin
17336.028:0150:0154:fixme:kernelbase:AppPolicyGetProcessTerminationMethod FFFFFFFFFFFFFFFA, 000000000011FEB0
17336.031:00e4:0328:warn:threadname:NtSetInformationThread Thread renamed to L"wine_threadpool_worker"
17336.050:0030:032c:warn:threadname:NtSetInformationThread Thread renamed to L"wine_threadpool_worker"
17336.051:0030:0330:warn:threadname:NtSetInformationThread Thread renamed to L"wine_threadpool_worker"
17336.052:0030:0338:warn:threadname:NtSetInformationThread Thread renamed to L"wine_threadpool_worker"
17336.052:0030:0334:warn:threadname:NtSetInformationThread Thread renamed to L"wine_threadpool_worker"
17336.052:0030:033c:warn:threadname:NtSetInformationThread Thread renamed to L"wine_threadpool_worker"
pid 109456 != 109455, skipping destruction (fork without exec?)Full log here: https://drive.proton.me/urls/9NXRH89QAM#tN34zNvXpxMv
System info here: https://gist.github.com/agurenko/5d0fbc28b11723092c1c30d410535f02
E-D-W-I-N
commented
6 months ago @E-D-W-I-N in what proton versions? Is this a new behavior? I assume there's some variability, but roughly how long does it take for these to occur? It would also be helpful for you to share your specifications and proton log.
Please add
PROTON_LOG=1 %command%to the game's launch options and attach the generated $HOME/steam-$APPID.log to this issue report as a file. You can retrieve a full system information report by clickingHelp>System Informationin the Steam client on your machine. Then upload it to Gist
Got some logs just a few minutes ago. Game just turns to completely black screen and won't close even through Steam's library (stop button).
Last lines before the end of the log:
16257.444:0120:01c4:warn:seh:dwarf_virtual_al_unwind next function rip=0000739ada396a3c
16257.444:0120:01c4:trace:unwind:dwarf_virtual_unwind rax=0000000000000000 rbx=0000739ada3191e0 rcx=0000739ad9a3df50 rdx=00007397d255f7c0
16257.444:0120:01c4:trace:unwind:dwarf_virtual_unwind rsi=0000000000000002 rdi=0000739a51a5d740 rbp=0000000000000000 rsp=0000000100d42950
16257.444:0120:01c4:trace:unwind:dwarf_virtual_unwind r8=0000000000000000 r9=00000000ffffffff r10=0000000000000000 r11=0000739ad85e82d0
16257.444:0120:01c4:trace:unwind:dwarf_virtuunwind backtrace: 0x739ada396a3c: /usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/libc.so.6 + 0x108a3c.
16257.444:0120:01c4:trace:unwind:execute_cfa_instructions 739ada396a35: DW_CFA_def_cfa %rsp, 8
16257.444:0120:01c4:trace:unwind:execute_cfa_instructions 739ada396a35: DW_CFA_offset %rip, -8
16257.444:0120:01c4:trace:unwind:dwarf_virtual_unwind fde 0x739ada45352c len 10 personality (nil) lsda (nil) code 739ada396a35-739ada396a46
16257.444:0120:01c4:trace:unwind:execute_cfa_instructions 739ada396a35: DW_CFA_undefined %rip
16257.444:0120:01c4:trace:unwind:dwarf_virtual_unwind r12=fffffffffffffb68 r13=0000000000000002 r14=00000001000ff880 r15=0000000100a00000
16257.444:0120:01c4:trace:unwind:dwarf_virtual_unwind function 739ada396a3c base 0x739ada396a35 cie 0x739ada43a7a0 len 14 id 0 version 1 aug 'zR' code_align 1 data_align -8 retaddr %rip
16257.444:0120:01c4:warn:seh:dwarf_virtual_unwind backtrace: 0x739ada396a3c: /usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/libc.so.6 + 0x108a3c.
16257.444:0120:01c4:trace:unwind:execute_cfa_instructions 739ada396a35: DW_CFA_def_cfa %rsp, 8
16257.444:0120:01c4:trace:unwind:execute_cfa_instructions 739ada396a35: DW_CFA_offset %rip, -8
16257.444:0120:01c4:trace:unwind:dwarf_virtual_unwind fde 0x739ada45352c len 10 personality (nil) lsda (nil) code 739ada396a35-739ada396a46
16257.444:0120:01c4:trace:unwind:execute_cfa_instructions 739ada396a35: DW_CFA_undefined %rip
16257.444:0120:01c4:trace:unwind:dwarf_virtual_unwind next function rip=0000739ada396a3c
16257.444:0120:01c4:trace:unwind:dwarf_virtual_unwind rax=0000000000000000 rbx=0000739ada3191e0 rcx=0000739ad9a3df50 rdx=00007397d255f7c0
16257.444:0120:01c4:trace:unwind:dwarf_virtual_unwind rsi=0000000000000002 rdi=0000739a51a5d740 rbp=0000000000000000 rsp=0000000100d42958
16257.444:0120:01c4:trace:unwind:dwarf_virtual_unwind r8=0000000000000000 r9=00000000ffffffff r10=0000000000000000 r11=0000739ad85e82d0
16257.444:0120:01c4:trace:unwind:dwarf_virtual_unwind r12=fffffffffffffb68 r13=0000000000000002 r14=00000001000ff880 r15=0000000100a00000
16257.444:0120:01c4:trace:unwind:dwarf_virtual_unwind function 739ada396a3c base 0x739ada396a35 cie 0x739ada43a7a0 len 14 id 0 version 1 aug 'zR' code_align 1 data_align -8 retaddr %rip
16257.444:0120:01c4:warn:seh:dwarf_virtual_unwind backtrace: 0x739ada396a3c: /usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/libc.so.6 + 0x108a3c.
16257.444:0120:01c4:trace:unwind:execute_cfa_instructions 739ada396a35: DW_CFA_def_cfa %rsp, 8
16257.444:0120:01c4:trace:unwind:execute_cfa_instructions 739ada396a35: DW_CFA_offset %rip, -8
16257.444:0120:01c4:trace:unwind:dwarf_virtual_unwind fde 0x739ada45352c len 10 personality (nil) lsda (nil) code 739ada396a35-739ada396a46
16257.444:0120:01c4:trace:unwind:execute_cfa_instructions 739ada396a35: DW_CFA_undefined %rip
16257.444:0120:01c4:trace:unwind:dwarf_virtual_unwind next function rip=0000739ada396a3c
16257.444:0120:01c4:trace:unwind:dwarf_virtual_unwind rax=0000000000000000 rbx=0000739ada3191e0 rcx=0000739ad9a3df50 rdx=00007397d255f7c0
16257.444:0120:01c4:trace:unwind:dwarf_virtual_unwind rsi=0000000000000002 rdi=0000739a51a5d740 rbp=0000000000000000 rsp=0000000100d42960
16257.444:0120:01c4:trace:unwind:dwarf_virtual_unwind r8=0000000000000000 r9=00000000ffffffff r10=0000000000000000 r11=0000739ad85e82d0
16257.444:0120:01c4:trace:unwind:dwarf_virtual_unwind r12=fffffffffffffb68 r13=0000000000000002 r14=00000001000ff880 r15=0000000100a00000
16257.444:0120:01c4:trace:unwind:dwarf_virtual_unwind function 739ada396a3c base 0x739ada396a35 cie 0x739ada43a7a0 len 14 id 0 version 1 aug 'zR' code_align 1 data_align -8 retaddr %rip
16257.444:0120:01c4:warn:seh:dwarf_virtual_unwind backtrace: 0x739ada396a3c: /usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/libc.so.6 + 0x108a3c.
pid 18929 != 18928, skipping destruction (fork without exec?)As I can see there's the same last line as in @agurenko's logs, pid's is the only difference
I've noticed that game is freezing way more often when I switch my workspaces (I'm using tiling WM) for example to change the music while I search for the match or smth. But sometimes game can freeze even if it's the only opened app in my system
I can attach the full log to Google drive or another service if you need it. GitHub is allowing only 25MB file, but my logs are 790MB :)
Here's my system info: https://gist.github.com/E-D-W-I-N/a90f9cabc4406a813d8fb4cbfd07bb82
polluxau
commented
6 months ago I recently experienced some freezes also in multiple games and found out that kernel 6.7 and 6.8 both freeze my computer with my amd card, using 6.6 LTS i havent experienced a single crash on any game yet and its been 2 days. Every time I go back to 6.7 or 6.8 i experience the same crashes
agurenko
commented
6 months ago Just a quick update from my side, I've forced Proton 8 after posting my logs and have not had any freezes since then
simifor
commented
6 months ago so you're both on amd and 6.8 kernel, one had luck with downgrading the kernel and the other with proton. @polluxau have you tried using proton 8 with kernel 6.8 to see if the issue still happens there?
E-D-W-I-N
commented
6 months ago so you're both on amd and 6.8 kernel, one had luck with downgrading the kernel and the other with proton. @polluxau have you tried using proton 8 with kernel 6.8 to see if the issue still happens there?
I'm third here 😂 on Nvidia. I'll try proton 8 today. Hope it helps
polluxau
commented
6 months ago so you're both on amd and 6.8 kernel, one had luck with downgrading the kernel and the other with proton. @polluxau have you tried using proton 8 with kernel 6.8 to see if the issue still happens there?
ill have a try, give me a couple of minutes
i have tested overwatch 2 for 30 minutes under kernel 6.8.1 with proton-ge8-32 as normal proton 8 has fps issues with amd cards
this was also tested under gnome 46 wayland, while the crashes i mentioned were on plasma 6 wayland so the cause of the problem could be plasma 6 wayland, not to do with the kernel or it could be a proton 9 issue, unsure still
also tested halo infinite under gnome 46 and latest proton experimental(bleeding edge) and it hasn't crashed, so the issue im talking about could be entirely different from the crashes you guys are getting, my conclusion is its kde plasma 6 wayland crashing randomly not the kernel or proton, ill be waiting for plasma 6.0.3 to come out in a few days to see if this occurs once again
Nanotwerp
commented
6 months ago Ever since about maybe 2 weeks ago, I've been experiencing the same issue as @agurenko and @E-D-W-I-N. I haven't encountered it again, though, after switching from the bleeding edge branch of Proton Experimental to GE-Proton9-1. I'll update this if the issue does happen again.
UPDATE 1: I'm now using GE-Proton9-2, and still haven't encountered the issue again after a freakishly long time of playing. I would recommend switching to this to anyone who has the same issue.
UPDATE 2: I encountered the issue again. It could be possibly related to me upgrading from GNOME 45 to GNOME 46. I'm also wondering if it's an issue specific to RDNA 2.
simifor
commented
6 months ago Yesterday I tried OW2 for around an hour and a half with proton 9 and linux 6.8.1 and couldn't get the game to freeze or crash, this was with a RDNA2 card.
ishitatsuyuki
commented
6 months ago Those experiencing freezes, can you try launching with WINE_DISABLE_KERNEL_WRITEWATCH=1?
ishitatsuyuki
commented
6 months ago Just tried this myself and got a hang with kernel write watch disabled, so looks like that's not the culprit.
Compatibility Report
System Information
I confirm:
Proton_LOG=1 https://gist.github.com/EpicureanGit/17ffca725b311bd1f78cb621c47e6efe
Symptoms
My cursor doesn't align with the interface after lowering my in-game resolution from my native 4K resolution. Under my native resolution the cursor aligns with the light gray highlighted "2560 X 1440 (60)*" resolution option.
After I changed my monitor resolution to "1920 x 1080 (60)" I had to move my cursor to the left and up in order to highlight the "2880 x 1620 (60)" resolution option.
Reproduction
In-game go to the lower right, select Menu, go to Options, and then go to Video. Then while using fullscreen display mode lower your resolution from your native resolution and apply the new settings.