ValveSoftware / ValveSoftware/Fossilize
Fossilize_replay vulkan bug, arch proton
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 780
- Forks
- 78
- PR merge metrics
- No merged PRs in 30d
Description
Relevant cross post in the Arch forums: https://bbs.archlinux.org/viewtopic.php?pid=2138103#p2138103
I have been trying to get Vulkan to work, after it went kaput today and games stopped working. Latest drivers, proton versions, etc...all up to date.
Trying to run vulkaninfo, yields Segmentation fault (core dumped)
gdb reports statement(program exited with code 0377)
(gdb) bt produces No stack.
The problem from core dumps hashes traces back to fossilize.
core dumps look normal except for :
'core.rundll32\x2eexe.1000{longhash_function_here}.zst
Which seems to correspond to "core.fossilize_repla.1000" hash (Steam's shader layer), from core dumps.
Is this bug or a feature?
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
No repository files or tests are named. Start by reproducing the vulkaninfo segmentation fault on Arch with the reported Vulkan drivers and Proton setup, then inspect the Fossilize-related core dump and gdb output. Done means isolating whether Fossilize is responsible and documenting a reproducible failure or a clearly actionable fix scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- computer-graphics
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100