That seems abnormally huge to me. Maybe this is a good lead to the issue. How much time did you play to generate this large of a log? Maybe you have a video card/driver issue? Did you set launch parameters in the game properties?
I played for under 20 minutes before crashing. There are no timestamps so I can’t say whether it all happened at once or over the course of those 20 minutes. However, my computer did take a veeery long time doing REISUB (like 30 seconds compared to near instantly) so I lean towards all at once at the end. Though, I did notice minor lag spikes throughout, so it could have been the whole time.
I am using Optimus, tried on my iGPU and got the crash as well.
Yes. I have tried with and without gamemoderun.
PROTON_LOG=1 gamemoderun %command%
I just tried playing for around 1-2 minutes, ended up with a 760MB file of similar logs. Here’s a sample:
2028.027:0124:0128:trace:unwind:dump_unwind_info unwind info at 00000001816E9F40 flags 0 prolog 0x19 bytes function 000000018078F1E0-000000018078F1F9
2028.027:0124:0128:trace:unwind:dump_unwind_info 0x19: subq $0x98,%rsp
2028.027:0124:0128:trace:unwind:dump_unwind_info 0xe: pushq %rbx
2028.027:0124:0128:trace:unwind:dump_unwind_info 0xd: pushq %rbp
2028.027:0124:0128:trace:unwind:RtlVirtualUnwind type 0 rip 18078f1d4 rsp 10ea40
2028.027:0124:0128:trace:unwind:dump_unwind_info **** func 78f1b0-78f1df
2028.027:0124:0128:trace:unwind:dump_unwind_info unwind info at 0000000181683B58 flags 0 prolog 0xa bytes function 000000018078F1B0-000000018078F1DF
2028.027:0124:0128:trace:unwind:dump_unwind_info 0xa: movq %rbx,0x30(%rsp)
2028.027:0124:0128:trace:unwind:dump_unwind_info 0xa: subq $0x20,%rsp
2028.027:0124:0128:trace:unwind:dump_unwind_info 0x6: pushq %rdi
2028.027:0124:0128:trace:unwind:RtlVirtualUnwind type 0 rip 18079736b rsp 10ea70
2028.027:0124:0128:trace:unwind:dump_unwind_info **** func 797140-79796a
2028.027:0124:0128:trace:unwind:dump_unwind_info unwind info at 00000001816EA764 flags 0 prolog 0x29 bytes function 0000000180797140-000000018079796A
2028.027:0124:0128:trace:unwind:dump_unwind_info 0x29: movq %rdi,0x10c8(%rsp)
2028.027:0124:0128:trace:unwind:dump_unwind_info 0x29: movq %rsi,0x10c0(%rsp)
2028.027:0124:0128:trace:unwind:dump_unwind_info 0x29: movq %rbx,0x10b8(%rsp)
2028.027:0124:0128:trace:unwind:dump_unwind_info 0x29: subq $0x1090,%rsp
2028.027:0124:0128:trace:unwind:dump_unwind_info 0x14: pushq %r15
2028.027:0124:0128:trace:unwind:dump_unwind_info 0x12: pushq %r14
2028.027:0124:0128:trace:unwind:dump_unwind_info 0x10: pushq %rbp
The log should not big that big, that indicates something is flooding it. At this point if the log is not shareable only you can look at it. What you posted is not relevant I think.
Filtering out the stacktrace portions I get several thousand lines of
3533.134:0120:0278:warn:seh:dispatch_exception EXCEPTION_WINE_CXX_EXCEPTION exception (code=e06d7363) raised
Error e06d7363 is a Windows exception relating to lack of permission to open a file.
I also found a couple lines at the beginning of
gamemodeauto: dlopen failed - libgamemode.so: cannot open shared object file: No such file or directory
So it seems that something somewhere has a permissions issue. Unfortunately, none of these logs tell me what specifically has this permissions issue. I used find to check the permissions of every single file in the game’s compatdata directory, but all of them have at least read/write permissions for my user.
This is expected warnings.
Give exact full info of everything possible at this point, I think you’re hiding some relevant information. Nothing makes sense to me. Something is not standard in your setup I think. How are you using your Nvidia card with your game? Where and how is Steam installed, where are the game installed and on which file system, and so on. Is the issue reproducible on a new user? How are system temperatures? How are system resources?
Give full information of everything possible so we can have a clearer picture of your system.
I play DRG on Nvidia since many years, it works without any issue on all Proton version.
I believe I have solved it (fingers crossed for real this time) by scrubbing every Steam-related file out of my system and doing a full reinstall of the client and all my games. No idea what the issue was.
Edit from the future: Happened again, scrubbing files didn’t work. I discovered that it is a bug with Optimus and Vulkan. I’m not sure why it happens only sometimes, but another useful fix is to disable DXVK for the game (PROTON_USE_WINED3D=1).
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.