Hello @myocytebd, can you check if /dev/shm is configured relatively normally and not hitting an extreme like being completely full?
Hello @myocytebd, can you check if /dev/shm is configured relatively normally and not hitting an extreme like being completely full?
I think it is configured properly with no artificial capacity limit.
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev,inode64)
Reading and writing files with a few GiB size at /dev/shm seems fine.
This is a blind guess, but try remounting /dev/shm without inode64 and see if that has an effect?
This is a blind guess, but try remounting /dev/shm without inode64 and see if that has an effect?
mount with inode32 workaround the problem -- steam client shows login UI.
So steam client is apparently bugged. And I would guess that maybe the stat struct definition is picked incorrectly?
Part of the strace log.
fstat64() succeeds but steam client complains "Error 75 getting shared memory size".
1624987 unlink("/dev/shm/u1000-ValveIPCSharedObj-Steam") = 0
1624987 openat(AT_FDCWD, "/dev/shm/u1000-ValveIPCSharedObj-Steam", O_RDWR|O_CREAT|O_LARGEFILE|O_NOFOLLOW|O_CLOEXEC, 0777) = 20
1624987 close(17) = 0
1624987 close(18) = 0
1624987 close(19) = 0
1624987 flock(20, LOCK_EX) = 0
1624987 fstat64(20, {st_mode=S_IFREG|0775, st_size=0, ...}) = 0
1624987 gettid() = 1624987
1624987 write(2, "Error 75 getting shared memory s"..., 35) = 35
1624987 close(20) = 0
A possible cause: (quote from tmpfs inode64 patch author)
https://chrisdown.name/2021/07/02/tmpfs-inode-corruption-introducing-inode64.html
So the problem is that if you have a 32-bit executable compiled without _FILE_OFFSET_BITS=64 on a system with a 64-bit wide ino_t, glibc's stat() will simply fail with EOVERFLOW for inode numbers greater than 2^32. As such, we need a support option for those who need to preserve this legacy behaviour while still allowing more modern systems to avoid this issue.
(Not every fstat syscall is followed by Error 75, so some fstat are correct and some are broken)
FWIW I tried manually deleting everything steam relating then doing a fresh reinstall from the official .deb, and got very similar results to 9762: https://gist.github.com/dubslow/3b100e8b2f8d796e3554216e77377ac6
Do I read that right that crash dumps are automatically uploaded to Valve?
I am suddenly unable to open Steam. It was working hours ago. Looks related to this issue.
Error 75 getting shared memory sizeError 75 getting shared memory sizesrc/common/html/chrome_ipc_client.cpp (1107) : !"Collided with existing master response stream"
src/common/html/chrome_ipc_client.cpp (1107) : !"Collided with existing master response stream"
Error 75 getting shared memory sizesrc/overlay/common/shmemdrop.h (151) : Assertion Failed: Failed creating file mapping SteamController_Master_mem
src/overlay/common/shmemdrop.h (151) : Assertion Failed: Failed creating file mapping SteamController_Master_mem
Error 75 getting shared memory sizesrc/overlay/common/shmemdrop.h (151) : Assertion Failed: Failed creating file mapping SteamController_Fast_Master_mem
src/overlay/common/shmemdrop.h (151) : Assertion Failed: Failed creating file mapping SteamController_Fast_Master_mem
Error 75 getting shared memory sizesrc/overlay/common/shmemdrop.h (151) : Assertion Failed: Failed creating file mapping SteamController_Slow_Master_mem
src/overlay/common/shmemdrop.h (151) : Assertion Failed: Failed creating file mapping SteamController_Slow_Master_mem
Error 75 getting shared memory sizesrc/overlay/common/shmemdrop.h (151) : Assertion Failed: Failed creating file mapping SteamController_Master_Cursor_mem
src/overlay/common/shmemdrop.h (151) : Assertion Failed: Failed creating file mapping SteamController_Master_Cursor_mem
Error 75 getting shared memory sizeError 75 getting shared memory sizeError 75 getting shared memory sizeError 75 getting shared memory sizesrc/overlay/common/shmemdrop.h (151) : Assertion Failed: Failed creating file mapping SteamController_Master_mem
src/overlay/common/shmemdrop.h (151) : Assertion Failed: Failed creating file mapping SteamController_Master_mem
Error 75 getting shared memory sizesrc/overlay/common/shmemdrop.h (151) : Assertion Failed: Failed creating file mapping SteamController_Fast_Master_mem
src/overlay/common/shmemdrop.h (151) : Assertion Failed: Failed creating file mapping SteamController_Fast_Master_mem
Error 75 getting shared memory sizesrc/overlay/common/shmemdrop.h (151) : Assertion Failed: Failed creating file mapping SteamController_Slow_Master_mem
src/overlay/common/shmemdrop.h (151) : Assertion Failed: Failed creating file mapping SteamController_Slow_Master_mem
Error 75 getting shared memory sizesrc/overlay/common/shmemdrop.h (151) : Assertion Failed: Failed creating file mapping SteamController_Master_Cursor_mem
src/overlay/common/shmemdrop.h (151) : Assertion Failed: Failed creating file mapping SteamController_Master_Cursor_mem
Error 75 getting shared memory sizeError 75 getting shared memory sizeError 75 getting shared memory sizeError 75 getting shared memory sizeError 75 getting shared memory sizesrc/common/html/chrome_ipc_client.cpp (1107) : !"Collided with existing master response stream"
src/common/html/chrome_ipc_client.cpp (1107) : !"Collided with existing master response stream"
Error 75 getting shared memory sizeError 75 getting shared memory sizesrc/common/html/chrome_ipc_client.cpp (1107) : !"Collided with existing master response stream"
src/common/html/chrome_ipc_client.cpp (1107) : !"Collided with existing master response stream"
Is there any way to work around this / roll back?
As of today, with a fresh apt-get dist-upgrade of Debian bookworm, steam now works again on my computer.
Closing as fixed in the 2023-09-11 Steam client update.
Nothing extracted yet.
Your system information
Unknown - due to crash on launch
Ubuntu 22.04
No
Yes
Please describe your issue in as much detail as possible:
Describe what you expected should happen and what did happen. Please link any large code pastes as a Github Gist
Steps for reproducing this issue:
Log
dmp.zip