-
Notifications
You must be signed in to change notification settings - Fork 47
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fossilize_replay dumped core #117
Comments
Segfaults on 3 different CPU threads
|
I got following entries after I ran The coredumps happened when I was playing Guild Wars 2 on Steam. the game hadn't crashes or suffered any issues, it's just that coredumps happened during that time. |
I get constant
Is this expected? |
I get coredumps of 1-9 fosslize_replay processes when launching Deep Rock Galactic. Sometimes, the "compiling shader" dialog get stuck and I have to manually skip/close it. Sometimes it continues, and sometimes fossilize_replay just doesn't crash and the shaders compile just fine. It doesn't seem to follow any pattern, really. I'm running an Intel Arc A770 with latest mesa drivers. EDT: This doesn't affect game performance, but weirdly enough sometimes the game hangs my graphics driver. I raised this issue with the mesa devs. As the hangs seem to be a regression in the driver and are not related to fosslize_replay's behaiviour, I think these issues are not related at the time of writting this.
|
Just realized this issue is 4 years old.. I am also seeing this issue on Arch Linux:
FWIW I don't play many games, mostly Dota2 and Warframe. |
Hello @Strykar, |
Thanks @kisak-valve but that is no longer the case today (
Still logging |
I've lately seen this for the first time:
I'm not sure how to decode this, I'm also seeing a similar dmesg output for Electron apps sometimes. The coredump isn't very helpful either because debug info seems missing:
Error 4 probably means user-space was faulting for a non-existing page (
PF_USER
).I copied the 489830 cache to my local build and try to reproduce now with this command:
It resulted in the following log: https://gist.github.com/kakra/0272aa4ca003836750c18e687d6e1bf3
Retry with a debug build?
The text was updated successfully, but these errors were encountered: