The stacks are messy so it's hard to say what's going on. libc incompatibility?
Frame Module Signature [Expand] Source
0 libc-2.17.so libc-2.17.so@0x821c1
1 @0xfa0802f0
2 libnvidia-glcore.so.334.21 libnvidia-glcore.so.334.21@0x1eef665
3 libGL.so.334.21 libGL.so.334.21@0xa8c1d
4 libGL.so.334.21 libGL.so.334.21@0xa8c1f
5 libc-2.17.so libc-2.17.so@0x778cb
6 libc-2.17.so libc-2.17.so@0x1ac000
7 libc-2.17.so libc-2.17.so@0x7dc26
8 libc-2.17.so libc-2.17.so@0x1ac000
9 ld-2.17.so ld-2.17.so@0x1030d
10 libc-2.17.so libc-2.17.so@0x15e7e
11 ld-2.17.so ld-2.17.so@0x672
12 ld-2.17.so ld-2.17.so@0x102cc
13 ld-2.17.so ld-2.17.so@0x20fc0
14 libc-2.17.so libc-2.17.so@0x15e7e
15 ld-2.17.so ld-2.17.so@0x8264
16 libc-2.17.so libc-2.17.so@0x15e7e
17 libxcb.so.1.1.0 libxcb.so.1.1.0@0x9299
There was one that started like this
Frame Module Signature [Expand] Source
0 libc-2.17.so libc-2.17.so@0x821c1
1 @0xf9f668e0
2 locale-archive locale-archive@0x17f665
3 libGL.so.334.21 libGL.so.334.21@0xa8c1d
4 libGL.so.334.21 libGL.so.334.21@0xa8c1f
They're pretty garbage-y though so whether there's actual data here is unclear.
Looks like the May 29th client is also affected here, after the June 3rd beta client was reported to be working for one of us and broken for another person. Probably not an issue created by a change in the steam client.
Update: This issue is a regression found in =x11-drivers/nvidia-drivers-334.21-r3, 337.25, and 340.17. Nvidia-drivers-331.79 is not affected.
Nothing extracted yet.
The June 5th steam beta update crashes with STEAM_RUNTIME=0 on gentoo linux. There is not an obvious cause. Can a dev take a peek at these crash reports and let me know where the crash is occuring?
NOTE: I'm not asking for a fix to be implemented, I'm asking for a hint as to what in the gentoo multilib package set is out of tolerance for steam.