ValveSoftware / steam-for-linux

Issue tracking for the Steam for Linux beta client
4.25k stars 175 forks source link

TF2 crash when opening loadout screen for specific class #3140

Closed zorael closed 7 years ago

zorael commented 10 years ago

Kubuntu saucy amd64. Machine is a Dell Latitude E6520 laptop with the game alternating between running on its Intel SNB graphics and on the discrete Nvidia GF119M (NVS 4200M) card. The crash is prevalent on both.

Often (but not always) when I open the loadout screen for the engineer, TF2 segfaults.

Noteworthy is that this character has an unusual Power Surge Data Mining helm equipped. I don't have hard data to back it up, but it seems to only happen after I've joined a game, left it, and then open the loadout screen. (I can't remember being disconnected by the crash.)

Terminal output is not very helpful.

ERROR: ld.so: object '/main/games/steam.linux/ubuntu12_64/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded: ignored.
Uploading dump (out-of-process) [proxy '']
/tmp/dumps/crash_20140204101957_1.dmp
CGameStreamThread: Added instance ID 13696 for appid 440
Game removed: AppID 440 "Team Fortress 2", ProcID 13385
/main/games/steam.linux/SteamApps/common/Team Fortress 2/hl2.sh: line 67: 13385 Segmentation fault      ${GAME_DEBUGGER} "${GAMEROOT}"/${GAMEEXE} "$@"
Focused window is now 0, 0
OnFocusWindowChanged to window type: k_EWindowTypeNonSteamDesktop, 0
Finished uploading minidump (out-of-process): success = yes
response: CrashID=bp-114715d0-e616-4d07-b538-05c152140204
pid 13697 != 13696, skipping destruction (fork without exec?)

dmesg:

[62785.450781] hl2_linux[13385]: segfault at 0 ip 0000000099ddd7ca sp 00000000ffe8f8a0 error 4 in client.so[98c2e000+1a10000]

System information:

Processor Information:
    Vendor:  GenuineIntel
    CPU Family:  0x6
    CPU Model:  0x2a
    CPU Stepping:  0x7
    CPU Type:  0x0
    Speed:  3300 Mhz
    8 logical processors
    4 physical processors
    HyperThreading:  Supported
    FCMOV:  Supported
    SSE2:  Supported
    SSE3:  Supported
    SSSE3:  Supported
    SSE4a:  Unsupported
    SSE41:  Supported
    SSE42:  Supported

Network Information:
    Network Speed:  

Operating System Version:
    Linux Mint 16 Petra (64 bit)
    Kernel Name:  Linux
    Kernel Version:  3.12.4-pf+
    X Server Vendor:  The X.Org Foundation
    X Server Release:  11405000
    X Window Manager:  KWin
    Steam Runtime Version:  steam-runtime-release_2013-10-23

Video Card:
    Driver:  Intel Open Source Technology Center Mesa DRI Intel(R) Sandybridge Mobile x86/MMX/SSE2

    Driver Version:  3.0 Mesa 10.1.0-devel (git-adaa5a6 saucy-oibaf-ppa+curaga)
    OpenGL Version: 3.0
    Desktop Color Depth: 24 bits per pixel
    Monitor Refresh Rate: 60 Hz
    VendorID:  0x10de
    DeviceID:  0x1056
    Number of Monitors:  1
    Number of Logical Video Cards:  2
    Primary Display Resolution:  1920 x 1080
    Desktop Resolution: 1920 x 1080
    Primary Display Size: 13.54" x 7.64"  (15.51" diag)
                                            34.4cm x 19.4cm  (39.4cm diag)
    Primary VRAM Not Detected

Sound card:
    Audio device: IDT 92HD90BXX

Memory:
    RAM:  7860 Mb

Miscellaneous:
    UI Language:  English
    LANG:  en_US.UTF-8
    Microphone:  Not set
    Total Hard Disk Space Available:  73695 Mb
    Largest Free Hard Disk Block:  10854 Mb

Installed software:

Recent Failure Reports:
    Tue Feb  4 09:05:01 2014 GMT: file ''/tmp/dumps/crash_20140204100447_2.dmp'', upload yes: ''CrashID=bp-f0b2f853-8077-4b6b-bc66-fa1312140204''
    Tue Feb  4 10:04:32 2014 GMT: file ''/tmp/dumps/crash_20140204101957_1.dmp'', upload yes: ''CrashID=bp-114715d0-e616-4d07-b538-05c152140204''
kisak-valve commented 7 years ago

Hello @zorael, are you still experiencing this issue on an up to date system?

zorael commented 7 years ago

I'm afraid I no longer use the laptop in question (battery died), so I can't test unless it's really really important.

kisak-valve commented 7 years ago

That's okay. If you happen to come across this issue again, you can open a new issue report in the Source-1-Games issue tracker and we can look into it further.