[Linux] [TF2] Crash to desktop after winning last round of MvM, every map, every time, since ToTC update

[gmjck]

Ever since the Tale of Two Cities update, I've been experiencing the following issue every time my team successfully completes the last wave of the game:

As soon as the Victory screen starts to appear, the Administrator's response (e.g., "We win! We win it all!") start to play. But as soon as the audio starts, it stutters for ~1 second, and then the game crashes to the desktop.

This has happens on every MvM I've tried (Mannhattan, Rottenburg, Decoy, Coal Town), and happens after every final wave victory.

While trying to gather more data, I brought up the ~ console a few seconds before my team beat the final tank on wave 6 of beginner Coal Town. They beat the tank, and nothing usual happened. The game played the Administrator's "We win it, we win it all!" fine, and the only new text that appeared in the console was something like "Updated lobby" (don't recall exact phrasing). No audio stutters or crash. However, as soon as I closed the console, the background music stuttered for a second and then the game crashed to the desktop. So it seems like the crash has something to do with what's being rendered on the Victory screen.

Linux Mint 15 / ATI HD 6870 / Catalyst 13.8 beta last night, 13.11 tonight, same issue. Occurred with the original ToTC update and with the 11/22 patch.

MvM had been playing perfectly. Played the day before the Tale of Two Cities update and had no crashes.

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

Network Information: Network Speed:

Operating System Version: Linux Mint 15 Olivia (64 bit) Kernel Name: Linux Kernel Version: 3.8.0-19-generic X Server Vendor: The X.Org Foundation X Server Release: 11303000 X Window Manager: Mutter (Muffin) Steam Runtime Version: steam-runtime-release_2013-10-23

Video Card: Driver: ATI Technologies Inc. AMD Radeon HD 6800 Series

Driver Version:  4.3.12614 Compatibility Profile Context 13.20.5
OpenGL Version: 4.3
Desktop Color Depth: 24 bits per pixel
Monitor Refresh Rate: 59 Hz
VendorID:  0x1002
DeviceID:  0x6738
Number of Monitors:  2
Number of Logical Video Cards:  1
Primary Display Resolution:  1920 x 1200
Desktop Resolution: 3840 x 1200
Primary Display Size: 20.39" x 12.76"  (24.02" diag)
                                        51.8cm x 32.4cm  (61.0cm diag)
Primary VRAM Not Detected

Sound card: Audio device: Realtek ALC1200

Memory: RAM: 3953 Mb

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

Installed software:

Recent Failure Reports:

---

Tail of output when running game from terminal (names anonymized):

Failed to find attachment point specified for particle effect in model 'models/bots\gibs\soldierbot_gib_boss_chest.mdl' keyvalues section. Trying to spawn effect 'flying_flaming_arrow_smoke' on attachment named 'smoke' [Me] killed Scout with machina. Cannot update control point 0 for effect 'player_sparkles_red'. [Me] killed Scout with bleed_kill. Giant Charged Soldier killed [A Player] with quake_rl. (crit) [Me] killed Scout with bleed_kill. [Me] killed Scout with bleed_kill. [Me] killed Scout with bleed_kill. [Me] killed Scout with bleed_kill. Failed to find attachment point specified for particle effect in model 'models/bots\gibs\soldierbot_gib_boss_chest.mdl' keyvalues section. Trying to spawn effect 'flying_flaming_arrow_smoke' on attachment named 'smoke' [A Player] killed Giant Charged Soldier with soda_popper. (crit) [Me] killed Scout with machina. (crit) [Me] killed Scout with bleed_kill. [Me] killed Scout with machina. (crit) [Me] killed Scout with bleed_kill. Sentry Buster killed [Me] with ullapool_caber. Sentry Buster killed [A Player] with ullapool_caber. [A Player] killed Sentry Buster with world. Scout killed [A Player] with scattergun. m_face->glyph->bitmap.width is 0 for ch:32 Verdana m_face->glyph->bitmap.width is 0 for ch:32 TF2 Build m_face->glyph->bitmap.width is 0 for ch:32 TF2 Build m_face->glyph->bitmap.width is 0 for ch:32 TF2 Build [A Player] : why doesn't it protect against busters ;-; [Me] killed Scout with machina. (crit) Failed to find attachment point specified for particle effect in model 'models/bots\gibs\soldierbot_gib_boss_chest.mdl' keyvalues section. Trying to spawn effect 'flying_flaming_arrow/[My Home Dir]/.local/share/Steam/SteamApps/common/Team Fortress 2/hl2.sh: line 67: 3189 Segmentation fault ${GAME_DEBUGGER} "${GAMEROOT}"/${GAMEEXE} "$@" Game removed: AppID 440 "Team Fortress 2", ProcID 3189

[dizietsma]

yes, i'm having exactly the same issue, admittedly i've had a few occasions in the past where i've just crashed to my linux desktop (incl steam client) apparently ramdomly; now i crash immediately upon winning the last wave in mvm.

system info:

Processor Information: Vendor: GenuineIntel CPU Family: 0x6 CPU Model: 0x3c CPU Stepping: 0x3 CPU Type: 0x0 Speed: 3401 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: "Mageia 3" (64 bit) Kernel Name: Linux Kernel Version: 3.8.13.4-server-1.mga3 X Server Vendor: The X.Org Foundation X Server Release: 11304000 X Window Manager: KWin Steam Runtime Version: steam-runtime-release_2013-10-23

Video Card: Driver: NVIDIA Corporation GeForce GTX 770/PCIe/SSE2

Driver Version:  4.3.0 NVIDIA 319.60
OpenGL Version: 4.3
Desktop Color Depth: 24 bits per pixel
Monitor Refresh Rate: 59 Hz
VendorID:  0x10de
DeviceID:  0x1184
Number of Monitors:  1
Number of Logical Video Cards:  1
Primary Display Resolution:  1920 x 1200
Desktop Resolution: 1920 x 1200
Primary Display Size: 20.39" x 12.76"  (24.02" diag)
                                        51.8cm x 32.4cm  (61.0cm diag)
Primary Bus: PCI Express 16x
Primary VRAM: 2048 MB
Supported MSAA Modes:  2x 4x 8x 16x 

Sound card: Audio device: AV200

Memory: RAM: 32104 Mb

Miscellaneous: UI Language: English LANG: en_GB.UTF-8 Microphone: Not set Total Hard Disk Space Available: 1877664 Mb Largest Free Hard Disk Block: 796363 Mb

Installed software:

Recent Failure Reports: Wed Nov 13 00:23:59 2013 GMT: file ''/tmp/dumps/crash_20131113001238_1.dmp'', upload no: ''HTTP response code said error'' Thu Nov 14 01:50:07 2013 GMT: file ''/tmp/dumps/assert_20131114015000_4.dmp'', upload yes: ''CrashID=bp-bbb83544-6122-46ef-917d-6f6902131113'' Thu Nov 14 05:01:55 2013 GMT: file ''/tmp/dumps/assert_20131114050114_4.dmp'', upload yes: ''CrashID=bp-aca61f75-9176-4fb1-81a4-449062131113'' Fri Nov 15 00:24:59 2013 GMT: file ''/tmp/dumps/crash_20131115002450_13.dmp'', upload yes: ''CrashID=bp-fdbfe782-1902-4b0d-b7eb-e4a3f2131114'' Fri Nov 15 18:12:52 2013 GMT: file ''/tmp/dumps/crash_20131115181044_4.dmp'', upload no: ''Couldn't connect to server'' Sat Nov 16 23:51:21 2013 GMT: file ''/tmp/dumps/assert_20131116235012_4.dmp'', upload no: ''Failure when receiving data from the peer'' Sun Nov 17 15:00:39 2013 GMT: file ''/tmp/dumps/crash_20131117150016_4.dmp'', upload yes: ''CrashID=bp-51b48acd-0d4f-4eb2-94c1-fbdc62131117'' Sun Nov 17 15:01:24 2013 GMT: file ''/tmp/dumps/crash_20131117150016_3.dmp'', upload yes: ''CrashID=bp-9dda5604-7102-4d4c-9d0d-f53742131117'' Sun Nov 17 15:16:27 2013 GMT: file ''/tmp/dumps/assert_20131117151558_4.dmp'', upload yes: ''CrashID=bp-0bca438a-2556-4959-9a21-00aa82131117'' Mon Nov 18 00:54:29 2013 GMT: file ''/tmp/dumps/crash_20131118005419_4.dmp'', upload yes: ''CrashID=bp-e4675d92-7a80-4fb8-889c-17bad2131117'' Tue Nov 19 01:04:00 2013 GMT: file ''/tmp/dumps/crash_20131119010345_4.dmp'', upload yes: ''CrashID=bp-397af3ab-be73-4337-8024-06de02131118'' Tue Nov 19 23:56:54 2013 GMT: file ''/tmp/dumps/crash_20131119235623_13.dmp'', upload yes: ''CrashID=bp-f6837534-8943-42b3-9914-66bbb2131119'' Wed Nov 20 03:57:36 2013 GMT: file ''/tmp/dumps/crash_20131120035721_4.dmp'', upload yes: ''CrashID=bp-4da8ad0f-d4f5-4397-8319-942382131119'' Wed Nov 20 04:24:37 2013 GMT: file ''/tmp/dumps/assert_20131120042328_4.dmp'', upload no: ''Failure when receiving data from the peer'' Thu Nov 21 06:58:11 2013 GMT: file ''/tmp/dumps/assert_20131121065804_4.dmp'', upload yes: ''CrashID=bp-10c63816-0a12-4b06-a152-f79db2131120'' Thu Nov 21 11:27:02 2013 GMT: file ''/tmp/dumps/assert_20131121112637_4.dmp'', upload yes: ''CrashID=bp-8bae5ce4-a020-439e-97b7-4c1572131121'' Thu Nov 21 17:29:43 2013 GMT: file ''/tmp/dumps/assert_20131121172827_4.dmp'', upload yes: ''CrashID=bp-a2830bee-d71f-4825-a4b4-e95042131121'' Thu Nov 21 21:03:49 2013 GMT: file ''/tmp/dumps/crash_20131121210349_13.dmp'', upload no: ''Failure when receiving data from the peer'' Thu Nov 21 22:58:00 2013 GMT: file ''/tmp/dumps/crash_20131121225738_4.dmp'', upload yes: ''CrashID=bp-a183a18e-59c4-4c0e-a5d3-caa862131121'' Sat Nov 23 00:12:15 2013 GMT: file ''/tmp/dumps/crash_20131123001159_4.dmp'', upload yes: ''CrashID=bp-848d78c7-21ed-48d4-962e-7a3b42131122'' Sat Nov 23 01:10:43 2013 GMT: file ''/tmp/dumps/crash_20131123001117_1.dmp'', upload no: ''Failure when receiving data from the peer'' Sat Nov 23 01:14:32 2013 GMT: file ''/tmp/dumps/assert_20131123011326_4.dmp'', upload no: ''Failure when receiving data from the peer'' Sat Nov 23 02:08:31 2013 GMT: file ''/tmp/dumps/crash_20131123011212_1.dmp'', upload yes: ''CrashID=bp-2e97bb35-bf66-440a-98c0-da2c42131122'' Sat Nov 23 03:59:33 2013 GMT: file ''/tmp/dumps/assert_20131123035926_4.dmp'', upload yes: ''CrashID=bp-e86aaa2c-d3c5-4d75-8981-126052131122'' Sat Nov 23 04:11:27 2013 GMT: file ''/tmp/dumps/crash_20131123025432_1.dmp'', upload no: ''Failure when receiving data from the peer'' Sat Nov 23 05:07:12 2013 GMT: file ''/tmp/dumps/crash_20131123041253_1.dmp'', upload no: ''Failure when receiving data from the peer''

[gmjck]

Failure report that I believe is associated with my most recent MvM crash:

Recent Failure Reports: Sat Nov 23 18:39:04 2013 GMT: file ''/tmp/dumps/assert_20131123133831_13.dmp'', upload yes: ''CrashID=bp-a176d951-2451-42f8-a328-462222131123''

[darkmatterbutterflies]

I wanted to be acutely sure, and I'm reasonably certain now that I'm affected, too. This is a harsh crash, too: full freeze and then immediate segfault. Nothing's catching any specific errors, and the terminal output jumps straight to the dump processes mid-line. I read several pages of my sentry gun killing bots and I don't see anything out of the ordinary leading up to the critical event:

Uploading dump (out-of-process) [proxy ''] /tmp/dumps/crash_20131123233020_1.dmp /home/thisguy/Steam/SteamApps/common/Team Fortress 2/hl2.sh: line 67: 3231 Segmentation fault (core dumped) ${GAME_DEBUGGER} "${GAMEROOT}"/${GAMEEXE} "$@"

This is going to sound like an insane question, but has anybody tried winning on a listenserver? You may want to sv_cheat a little to make such a thing possible, but it might help corner the issue a little. If the game halts and segfaults upon player victory on a listenserver, then something about the victory event for MVM period is now broken for the Linux client. If not, then it's some server-client interaction at the event that's causing the issue... or that's my reasoning.

[Cheogh]

I'm having this crash too

Processor Information: Vendor: AuthenticAMD CPU Family: 0x10 CPU Model: 0x4 CPU Stepping: 0x2 CPU Type: 0x0 Speed: 2600 Mhz 4 logical processors 4 physical processors HyperThreading: Unsupported FCMOV: Supported SSE2: Supported SSE3: Supported SSSE3: Unsupported SSE4a: Supported SSE41: Unsupported SSE42: Unsupported

Network Information: Network Speed:

Operating System Version: "Arch Linux" (64 bit) Kernel Name: Linux Kernel Version: 3.12.1-1-ARCH X Server Vendor: The X.Org Foundation X Server Release: 11404000 X Window Manager: KWin Steam Runtime Version: steam-runtime-release_2013-10-23

Video Card: Driver: NVIDIA Corporation GeForce GT 640/PCIe/SSE2

Driver Version:  4.4.0 NVIDIA 331.20
OpenGL Version: 4.4
Desktop Color Depth: 24 bits per pixel
Monitor Refresh Rate: 60 Hz
VendorID:  0x10de
DeviceID:  0xfc1
Number of Monitors:  1
Number of Logical Video Cards:  1
Primary Display Resolution:  1920 x 1080
Desktop Resolution: 1920 x 1080
Primary Display Size: 20.04" x 11.26"  (22.95" diag)
                                        50.9cm x 28.6cm  (58.3cm diag)
Primary Bus: PCI Express 16x
Primary VRAM: 2048 MB
Supported MSAA Modes:  2x 4x 8x 16x 

Sound card: Audio device: Realtek ALC1200

Memory: RAM: 5972 Mb

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

Installed software:

Recent Failure Reports: Mon Nov 25 23:47:53 2013 GMT: file ''/tmp/dumps/crash_20131125150448_1.dmp'', upload yes: ''CrashID=bp-fa6a0bfc-929b-4ee4-80e3-eac712131125''

[darkmatterbutterflies]

Today's patch fixed was recorded to have fixed a bug with the return-to-lobby timer, and I had hoped that the same bug was responsible for this crash. The issue, sadly, persists.

[powerlord]

Word on Reddit is that this is also happening on OSX.

[lumiera]

Bug still exists as of today.

[gmjck]

There is something of a work-around, though it's only practical if your team can handle the last few seconds of the final wave without your active support:

Just before beating the last wave, open the ~ console. Once your teammates complete the wave, enter the following console command: "hud_reloadscheme". You can the close the console and return to the game. You won't see the normal end game stats screen, but you can bring up the TAB scoreboard like normal.

This works for Boot Camp mode, don't know if there's any addition issue with Mann Up.

Apparently this was an issue for Windows users back in late August/early September. Here's the Steam Community forum thread where I found the console command tip:

http://steamcommunity.com/app/440/discussions/1/864977479802979832/

In that thread, someone mentioned that the issue was resolved in the following Sept. 5th patch:

http://www.teamfortress.com/post.php?id=11404

Hopefully it's the same/similar bug that's made its way to the Linux (and possibly OSX) version, and will be easy to resolve when developers are back from Thanksgiving.

[lumiera]

CrashID=bp-f7fd11ec-a2b3-45c6-a861-8b7322131130

[Half-Shot]

Don't think there is any need for me to add any specifics other than i'm having issues regarding:

• Crash pretty much mid sentence of the announcer saying victory "Vict-"
• I get a crash on clicking on the options menu more or less everytime. Probably unrelated.

[ericwomer]

I have the exact same issue, as soon as the match is over the game crashes.

System Specs: https://gist.github.com/salamanderrake/5c64ab09598d82fe29f9

[darkmatterbutterflies]

So I've been testing gmjck's workaround and I've found something that seems to work even better: just open the console. That's it, just open it and leave it open. This prevents the game from rendering the window, which is what I've come to believe is responsible for the crash. This could have something new they added that's interacting with openGL catastrophically, but that's just my hypothesis.

Recap: just before victory, open console and stare at it. Don't let the game render the (accused) bugged victory window.

[Half-Shot]

Makes sense. Nice workaround, wonder if there is a way to disable the victory screen itself.

darkmatterbutterflies notifications@github.com wrote:

So I've been testing gmjck's workaround and I've found something that seems to work even better: just open the console. That's it, just open it and leave it open. This prevents the game from rendering the window, which is what I've come to believe is responsible for the crash. This could have something new they added that's interacting with openGL catastrophically, but that's just my hypothesis.

Recap: just before victory, open console and stare at it. Don't let the game render the (accused) bugged victory window.

— Reply to this email directly or view it on GitHub.

[gmjck]

Yep, the only reason to do hud_reloadscheme is if you want to go back into the game to look at the final scoreboard.

[jorgenpt]

Should be resolved in an upcoming release.

[Cheeseness]

Looks like it's resolved with the recent update :D

[Half-Shot]

Seconding, although the options menu bug still persists for me.

[gmjck]

Yes, tonight's update does appear to fix the bug. Thanks!

[darkmatterbutterflies]

Seconding gmjck. The full Mann-Up Mode version of the victory sequence is also stable for me now. Capital! If somebody could check the Mac side of this, we can put a fork in this one.

[johndrinkwater]

Thanks for confirming, will close :)