Please provide crash dump IDs for investigation.
Just the IDs as recorded in the log in /tmp/dumps? Here are a few days' worth of them (those which I can match up with kernel log messages):
bp-4bd1bd46-0ed9-46a0-8a91-de6452240919
bp-c1cec302-25e2-4070-9205-0ddd72240919
bp-41d62491-731f-45fe-9fb5-dee632240919
bp-e3293290-6c52-4758-9b8f-b42c02240919
bp-17fb92ad-41c9-4f7d-a343-dcddc2240919
bp-80099bbc-dae1-48cd-8390-dbc002240919
bp-237bf950-1026-46e5-972b-bd2912240919
bp-00049635-e671-4b0d-b10e-c960d2240919
bp-9a695a66-2799-4d41-ab8e-98cc72240919
bp-1d495522-28dd-4ab8-9eaa-11a1f2240919
bp-6119670e-2eb3-4959-b498-ad7052240920
bp-24a26a9a-0c2e-4eec-a7b4-04f6e2240920
bp-62a4695c-f5cc-4e9e-885d-faffe2240920
bp-4a2d2c03-bead-4ae4-8134-2b74d2240920
bp-0b08eef9-fe0b-4c33-8869-3e1ce2240920
bp-1329e37c-ccc9-401b-8139-932d62240920
bp-1417c481-cead-4aeb-aa5a-f216d2240920
bp-8bd020b8-eeab-477f-a2b2-001d02240920
bp-10b666a7-c81b-422c-91df-caceb2240920
bp-85c0b99c-527e-411c-8fcf-3f3f92240920
bp-de1d6292-39b4-426e-877c-014f42240920
bp-89f7bc23-4de6-4df0-a003-60d3e2240920
bp-9397656c-4991-4161-abe8-f285b2240921
bp-40942470-39d3-4466-991b-cce402240921
bp-c2724534-fe53-43ba-be99-1e3032240921
bp-6b165208-f79d-49b1-81d4-e44ca2240921
Thanks. We are able to match this problem for other users too, across various distributions including SteamOS.
[423804.146107] CHTTPClientThre[30754]: segfault at e66fb0af ip 00000000e66fb0af sp 00000000d00d4c90 error 14 likely on CPU 2 (core 2, socket 0)
[423804.146116] Code: Unable to access opcode bytes at 0xe66fb085.
I just encountered this on Gentoo.
Seeing similar (or identical?) crashes again. Identifiers for the most recent three:
bp-3d36a74d-1c36-4bef-8cdb-371132250721
bp-0d3f2df2-bf27-4ba5-bfd4-6c50c2250722
bp-d4723526-b5d1-432e-95b2-90fb12250723
Kernel log text for the most recent one:
CHTTPClientThre[25030]: segfault at da41bb84 ip 00000000da41bb84 sp 00000000c1bfb890 error 14 likely on CPU 7 (core 1, socket 0)
Code: Unable to access opcode bytes at 0xda41bb5a.
CHTTPClientThre[25144]: segfault at f76e894c ip 00000000f7bfee38 sp 00000000b7efc2e0 error 4
CHTTPClientThre[25064]: segfault at f768dc60 ip 00000000f768dc60 sp 00000000c09fc3bc error 14
in libc.so.6[93e38,f7b8e000+189000] likely on CPU 5 (core 6, socket 0)
likely on CPU 8 (core 2, socket 0)
Code: Unable to access opcode bytes at 0xf768dc36.
Code: 8b 5c 24 10 8b 43 0c 89 c2 81 e2 7f 01 00 00 83 e0 7c 0f 85 aa 00 00 00 85 d2 0f 85 b2 00 00 00 8b 86 08 1b 00 00 85 c0 75 50 <8b> 43 0c 25 80 00 00 00 89 c1 75 10 65 a1 0c 00 00 00 85 c0 75 06
Environment is Devuan excalibur (which is, largely, Debian trixie).
CHTTPClientThre[12269]: segfault at de5b7924 ip 00000000de5b7924 sp 00000000bb2fa790 error 14 likely on CPU 8 (core 2, socket 0)
Code: Unable to access opcode bytes at 0xde5b78fa.
Nothing extracted yet.
This appears always to co-incides with exiting Steam.
Typical kernel log entry:
Occasionally, it looks like this instead:
It looks like the bug has been biting since 12 Sep, though there are a few instances of what may be the same issue between 4 Sep and 6 Sep:
Running the current beta client on Devuan stable; AMD hardware.