ValveSoftware / ValveSoftware/Proton
Cult of the Lamb (1313140)
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 32.8k
- Forks
- 1.6k
- PR merge metrics
- PR metrics pending
Description
Compatibility Report
- Name of the game with compatibility issues: Cult of the Lamb
- Steam AppID of the game: 1313140
System Information
- GPU: RTX 2080 Ti
- Driver/LLVM version: 530.41.03 (Open-GPU Kernel Module) - (Also happens with version 525.116.03)
- Kernel version: 6.2.7-273-tkg-pds
- Link to full system information report as: Gist
- Proton version: 8.0-1d
I confirm:
- that I haven't found an existing compatibility report for this game.
- that I have checked whether there are updates for my system available.
Symptoms
After playing the game for a relatively short amount of time, the game freezes and starts having audio played in a loop.
What's worse, the entire system freezes, requiring a hard system reboot.
Around the time it occurs, I imagine this access violation error is thrown in the log:
. . .
4836.645:0138:013c:warn:seh:dispatch_exception backtrace: --- Exception 0xc0000005.
4836.645:0138:013c:trace:seh:dispatch_exception code=c0000005 flags=0 addr=0000000076C0BAD6 ip=76c0bad6
4836.645:0138:013c:trace:seh:dispatch_exception info[0]=0000000000000000
4836.645:0138:013c:trace:seh:dispatch_exception info[1]=0000000000000000
4836.645:0138:013c:warn:seh:dispatch_exception EXCEPTION_ACCESS_VIOLATION exception (code=c0000005) raised
4836.645:0138:013c:trace:seh:dispatch_exception rax=0000000000000000 rbx=000000000010f610 rcx=0000000000000000 rdx=00000001063de7f8
4836.645:0138:013c:trace:seh:dispatch_exception rsi=0000000000000000 rdi=000000016dbbd420 rbp=000000000010efa0 rsp=000000000010ef70
4836.645:0138:013c:trace:seh:dispatch_exception r8=0000000000000000 r9=0000000000000000 r10=0000007eafff7eff r11=00000000767ff670
4836.645:0138:013c:trace:seh:dispatch_exception r12=000000000010f680 r13=000000016dbbd420 r14=0000000000000003 r15=0000000000000005
4836.645:0138:013c:trace:seh:call_vectored_handlers calling handler at 000000035906B310 code=c0000005 flags=0
4836.645:0138:013c:trace:seh:call_vectored_handlers handler at 000000035906B310 returned 0
4836.645:0138:013c:trace:seh:call_vectored_handlers calling handler at 00000002EDF1C040 code=c0000005 flags=0
4836.645:0138:013c:trace:seh:call_vectored_handlers handler at 00000002EDF1C040 returned 0
4836.645:0138:013c:trace:seh:call_vectored_handlers calling handler at 00000000624239A0 code=c0000005 flags=0
4836.645:0138:013c:trace:seh:call_vectored_handlers handler at 00000000624239A0 returned ffffffff
4840.078:0138:013c:trace:seh:RtlGrowFunctionTable 0000000329ACE690, 13
4840.078:0138:013c:trace:seh:RtlGrowFunctionTable 0000000329ACE690, 14
4840.078:0138:013c:trace:seh:RtlGrowFunctionTable 0000000329ACE690, 15
4840.078:0138:013c:trace:seh:RtlGrowFunctionTable 0000000329ACE690, 16
4840.078:0138:013c:trace:seh:RtlGrowFunctionTable 0000000329ACE690, 17
4840.078:0138:013c:trace:seh:RtlGrowFunctionTable 0000000329ACE690, 18
4840.078:0138:013c:trace:seh:RtlGrowFunctionTable 0000000329ACE690, 19
4840.078:0138:013c:warn:seh:dispatch_exception backtrace: --- Exception 0xc0000005.
4840.078:0138:013c:trace:seh:dispatch_exception code=c0000005 flags=0 addr=0000000076C0BAD6 ip=76c0bad6
4840.078:0138:013c:trace:seh:dispatch_exception info[0]=0000000000000000
4840.078:0138:013c:trace:seh:dispatch_exception info[1]=0000000000000000
4840.078:0138:013c:warn:seh:dispatch_exception EXCEPTION_ACCESS_VIOLATION exception (code=c0000005) raised
. . .
Reproduction
- Launch the game
- Play the game for about ~30 minutes or less
(when it specifically happens is unknown but it doesn't take long to trigger in normal gameplay)
(Usually happens at the player's camp, from what I've experienced)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Begin with the attached steam-1313140.log and the listed reproduction steps; compare the access-violation entries with the reported system, driver, kernel, and Proton details. Done means the game no longer freezes the system or loops audio during roughly 30 minutes of normal play, especially at the player's camp, on the reported setup.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100