Your system information

• Steam client version (build number or date): 1709846872
• Distribution (e.g. Ubuntu): Pop!_OS 22.04
• Opted into Steam client beta?: No
• Have you checked for system updates?: Yes
• Steam Logs: (excerpts below, can repro & provide more when needed)
• GPU: AMD (7900XTX)

Please describe your issue in as much detail as possible:

Monster Hunter World (582010) causes steam to crash after failing to connect to multiple online game sessions. Notably, the game continues running after Steam has exited, until the game freezes when attempting to use steam networking again.

Steps for reproducing this issue:

1. Launch MHW, use "Filter search" to attempt to join sessions
2. Choose sessions which are nearly full (13-16 players) for a specific quest type (easily repro'd myself for "Safi'jiva")
3. Attempt to join one, wait for the timeout, attempt to join another, repeat

Relevant? steam logs:

STEAMPS3 - AsyncTCPSocket created
...
STEAMPS3 - AsncTCPSocket destroyed
...

(thousands of these after only a few attempts to join a session)

STEAMPS3 - AsyncTCPSocket created
STEAMPS3 - AsyncTCPSocket created
*** buffer overflow detected ***: terminated
crash_20240414010808_65.dmp[119538]: Uploading dump (out-of-process)
/tmp/dumps/crash_20240414010808_65.dmp
/home/robo/.steam/debian-installation/steam.sh: line 813: 107466 Aborted                 (core dumped) "$STEAMROOT/$STEAMEXEPATH" "$@"
crash_20240414010808_65.dmp[119538]: Finished uploading minidump (out-of-process): success = yes
crash_20240414010808_65.dmp[119538]: response: CrashID=bp-f1c0a9d3-d636-4421-8548-e900d2240413
crash_20240414010808_65.dmp[119538]: file ''/tmp/dumps/crash_20240414010808_65.dmp'', upload yes: ''CrashID=bp-f1c0a9d3-d636-4421-8548-e900d2240413''
src/common/html/chrome_ipc_client.cpp (1113) : Failed to connect to master html process, created shared memory (spawn time 157.82)
04/14 01:08:13 Init: Installing breakpad exception handler for appid(gameoverlayui)/version(1.0)/tid(118115)
assert_20240414010813_7.dmp[119644]: Uploading dump (out-of-process)
/tmp/dumps/assert_20240414010813_7.dmp
assert_20240414010813_7.dmp[119644]: Finished uploading minidump (out-of-process): success = yes
assert_20240414010813_7.dmp[119644]: response: Discarded=1
assert_20240414010813_7.dmp[119644]: file ''/tmp/dumps/assert_20240414010813_7.dmp'', upload yes: ''Discarded=1''
src/common/pipes.cpp (883) : fatal stalled cross-thread pipe (pipe is disconnected).
src/common/pipes.cpp (883) : Fatal assert; application exiting
04/14 01:09:57 Init: Installing breakpad exception handler for appid(gameoverlayui)/version(1.0)/tid(118115)
assert_20240414010957_10.dmp[119823]: Uploading dump (out-of-process)
/tmp/dumps/assert_20240414010957_10.dmp
assert_20240414010957_10.dmp[119823]: Finished uploading minidump (out-of-process): success = yes
assert_20240414010957_10.dmp[119823]: response: Discarded=1
assert_20240414010957_10.dmp[119823]: file ''/tmp/dumps/assert_20240414010957_10.dmp'', upload yes: ''Discarded=1''
src/common/pipes.cpp (883) : fatal stalled cross-thread pipe (pipe is disconnected).
src/common/pipes.cpp (883) : Fatal assert; application exiting
ERROR: ld.so: object 'libgamemodeauto.so.0' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
assert_20240414010957_3.dmp[119826]: Uploading dump (out-of-process)
/tmp/dumps/assert_20240414010957_3.dmp
pid 117969 != 117968, skipping destruction (fork without exec?)
assert_20240414010957_3.dmp[119826]: Finished uploading minidump (out-of-process): success = yes
assert_20240414010957_3.dmp[119826]: response: Discarded=1
assert_20240414010957_3.dmp[119826]: file ''/tmp/dumps/assert_20240414010957_3.dmp'', upload yes: ''Discarded=1''
pid 119826 != 119825, skipping destruction (fork without exec?)

Tried:

• Disabling or disconnecting all but a single wired network interface
• Multiple Proton versions, 8, 9, GE-8, GE-9, etc...
• Reinstalling the game
• Obvious full system reboots, updates, newer mesa & graphics drivers, etc.

My expectation would be that steam should not outright crash if a game does not use networking sockets correctly, which might be happening here? Perhaps the attempted & failed sockets aren't cleaned up?