Team Fortress 2 stops responding on loading screen

steamclosed MOVED: Team Fortress 2reviewedWindow manager

ValveSoftware/steam-for-linux#2294 · opened 2013-04-09 by kerrickstaley · updated 2019-07-18 · 9 comments · github

Kkerrickstaley 2013-04-09 github

When TF2 is loading a map, it apparently stops processing GUI events for several seconds, causing this error dialog:

“Team Fortress 2 - OpenGL” is not responding.

You may choose to wait a short while for it to continue
or force the application to quit entirely.

                                 [Force Quit]  [Wait]

If you click "Wait", the map eventually loads successfully, but the pop-up is annoying.

Jjohndrinkwater 2013-04-09 github

Hi, could you add your system information as requested here please ‐ https://github.com/ValveSoftware/steam-for-linux#reporting-issues
You’re using GNOME ?

Jjohndrinkwater 2013-04-09 github

@monsterdan5 system information please! Are you on a slower machine?

Ttombsar 2013-04-25 github

This has been a problem for me in both the Windows and Linux non-beta versions for several years (but only results in the error message with certain window managers).

Basically, the program stops redrawing itself while loading the game files, leaving the 'Cancel' button useless, and the progress bar out of date (normally showing 'Retrieving Server Info').

I have made measurements that show the process is not CPU bound (data available on request), so I can only assume the main event thread is blocking on IO.

Mmagcius 2013-05-01 github

It seems the issue is that when TF2 loads, it does synchronous IO (possibly uploading to the GPU), so it can't respond to _NET_WM_PING requests from the WM.

It's unfortunate, but games really need to respond to X events, else things like this will happen.

Ddoug65536 2013-05-02 github

The same issue exists in Windows, due to not getting window messages from the message queue while loading a map. TF2 is loading the game with the GUI thread. I have the issue on a Core I7 990X Extreme Edition 6-core (12 thread) @ 3.46 GHz with GTX 580 SLI configuration, loading from a 10000 RPM hard drive with 20GB of RAM, so it's obviously just not servicing the message queue while loading.

Ppolochamps 2015-01-27 github

I had the same error you mentioned but only appears when launching the game.
I fixed it by removing the "-novid" in launch options

on
__GL_THREADED_OPTIMIZATIONS=1 %command% -novid

into
__GL_THREADED_OPTIMIZATIONS=1 %command%

Kkisak-valve maintainer 2017-04-26 github

Hello, is anyone still experiencing this issue with an up to date system?

?ghost 2017-05-25 github

I'm having the same problem. Using Ubuntu Gnome and the -novid launch option

OS: Ubuntu 17.04 zesty
Kernel: x86_64 Linux 4.10.0-21-generic
Resolution: 1920x1080
CPU: Intel Core i7-6700K CPU @ 4.2GHz
GPU: GeForce GTX 980 Ti
RAM: 3803MiB / 15997MiB
nVidia Drivers: 375.39

Kkisak-valve maintainer 2017-05-25 github

Hello @hhiru, thanks for testing. I've gone ahead and transferred @Polochamps and your comment to the Source-1-Games issue tracker. Let's track the -novid issue at https://github.com/ValveSoftware/Source-1-Games/issues/2280.

Launch options

__GL_THREADED_OPTIMIZATIONS=1x1 2015-01

Launch lines

__GL_THREADED_OPTIMIZATIONS=1 %command%x1 2015-01
__GL_THREADED_OPTIMIZATIONS=1 %command% -novidx1 2015-01