Awesomenauts freezes/CTD when using the Steam overlay

[terzag]

I have an issue with Awesomenauts that might have appeared at some point (i.e. I didn't encountered it monthes ago but got back to the game recently and can reproduce it at will).

The problem is simple: when opening/closing the Steam overlay, the game crashes to desktop or completely freezes and I have to kill the process. It happens randomly, not everytime I use the overlay but quite often (even on the same menu in game: I can open/close the overlay without problem then immediately do it again and the game will crash).

Here is the relevant part of what is displayed in the terminal before the game crashes:

=================== FrameHandler switching state ===================

PCGLOggVideoGraphicsAdapter destructor starts PCGLOggVideoGraphicsAdapter destructor ends OggVideoGraphicsAdapter destructor starts OggVideoGraphicsAdapter destructor ends MenuManager constructor starts, startScreen: 10 PopupMenuManager constructor starts PopupMenuManager constructor ends MenuManager constructor ends SceneManager::deleteAllCopiesForRendering starts SceneManager::deleteAllCopiesForRendering ends SaveGameManager: Loading SaveGameManager: Trying to load save file GLRenderTexture constructor starts 640x360 GLRenderTexture constructor ends GLRenderTexture constructor starts 640x360 GLRenderTexture constructor ends GLRenderTexture constructor starts 1920x1080 GLRenderTexture constructor ends Loaded from savegame: Prestige: 0 Gold: 536424 Saving season games started timestamp: 13884 X Error of failed request: BadWindow (invalid Window parameter) Major opcode of failed request: 25 (X_SendEvent) Resource id in failed request: 0x1400009 Serial number of failed request: 469 Current serial number in output stream: 46998168 Saving season games won timestamp: 1388498168 LeavePercentageManager::onLoadStats started 45 finished 41 finished this season 4 leave % 8.88889 Uploading new mean score of 3.63919 Uploading new stddev score of 0.877811 Saving mean stat: 3.63919 Saving stddev stat: 0.877811 Saving timestamp stat: 1388498168 Saving rank period: 7 RatingSynchroniser: Rating from Stats 10490.1 Rating from Leaderboards 10490 Local player ranking from stats: 3.63919 0.877811 found: 1 1 Rank timestamp: 1388498168 Found: 1 period: 7 period found: 1 Starting menu music "MusicMenuLoop.wav" Changed input controls from ControllerIndex 0 to Keyboard PlayerControllerIndex SystemManager: Overlay state changed: 1 0 0 1 SystemManager: Overlay state changed: 0 0 0 0 SystemManager: Overlay state changed: 1 0 0 1 SystemManager: Overlay state changed: 0 0 0 0 Changed input controls from Keyboard PlayerControllerIndex to ControllerIndex 0 Changed input controls from ControllerIndex 0 to Keyboard PlayerControllerIndex SystemManager: Overlay state changed: 1 0 0 1 SystemManager: Overlay state changed: 0 0 0 0 Inconsistency detected by ld.so: dl-close.c: 765: _dl_close: Assertion `map->l_init_called' failed! Game removed: AppID 204300 "Awesomenauts", ProcID 4492

The big problem seems to be that last line about dl-close.c

I have opened a thread on the game forum (http://www.awesomenauts.com/forum/viewtopic.php?f=13&t=25453&p=313620) though the developers don't think the issue comes from the game. Another player seems to have a similar problem (http://www.awesomenauts.com/forum/viewtopic.php?f=13&t=25822).

The issue might come from the game, Steam or the ATI Catalyst driver. The latter being the most likely.

Using Ubuntu 13.10 64 bit. Radeon HD 7770 with Catalyst 13.11 beta 9.95 from ATI website.

Note that I havent encountered similar overlay issues with other games.

[gdrewb-valve]

Valve note: works correctly for me on Ubuntu 12.04 / NVIDIA.

[terzag]

Problem is still present with the new Catalyst 14.1 beta (with regular Steam client and beta Steam client).

[bdmayes]

I'm experiencing this issue with a GTX 650 Ti and the 319.60 drivers (64-bit Ubuntu 13.10). So I don't think it's specific to ATI. I agree it's random. I just used it to send a message to someone and it worked fine. Then I hit it again, sent a message, and when I hit shift+tab to go back into Awesomenauts the process just died. I assume a segfault?

I'll try some things to see if it's specific to Awesomenauts or if it's the steam overlay in general. I can also try launching from terminal. That might give me some additional goodness printed to STDOUT/STDERR that I otherwise don't see.

[terzag]

As said above, I've reported the problem to the devs. They advised me to wait for the next game update (2.2, which is due "soon"), as they're switching to a newer version of the Steam API, and check if the problem still happens. I'll report here when the game is updated.

[bdmayes]

Yeah I saw that. FYI, I see nearly verbatim output when launching steam from terminal. I don't find anything that looks terribly relevant in the awesomenauts logs. I have tried:

1. Running steam using GAME_DEBUGGER=gdb steam and it just dies. In the past I have been able to hit some exception and then print the backtrace, but it doesn't even seem to drop into gdb when it crashes. :(
2. Setting ulimit -c to unlimited and then trying to get a core dump. It doesn't seem to dump when the game exits though??? I don't know why.

I also found some gameoverlay*.log files in /tmp but they don't seem to say much (an example of my gameoverlayui.log file is below). I guess we'll just have to wait for 2.2 and see if fixes the issue. For now I'll just avoid using the overlay as much as possible...

Sat Feb 15 23:51:10 2014 UTC - Overlay enable requested by game Sat Feb 15 23:51:10 2014 UTC - Overlay disable requested by game Sat Feb 15 23:51:11 2014 UTC - Overlay enable requested by game Sat Feb 15 23:51:13 2014 UTC - Overlay disable requested by game Sat Feb 15 23:51:14 2014 UTC - Overlay enable requested by game Sat Feb 15 23:51:14 2014 UTC - Overlay disable requested by game Sat Feb 15 23:51:15 2014 UTC - Game Exit Event signaled. Sat Feb 15 23:51:15 2014 UTC - Shutting down overlay

[terzag]

The problem is still present in Awesomenauts 2.2, which uses a new version of the Steam API.

[dtanderson]

I have the same issue if I try to invite a friend or pull the Steam overlay up to accept an invite, everything just freezes and I have to kill the game. I am running Ubuntu 14.04 64-bit and previously was running Ubuntu 13.10 64-bit and had the same problem. I have a Nvidia video card (GTX 650 Ti) and 331.38 video drivers.

[davad]

Same issue. Some game sessions it seems to freeze more often than work correctly. Others I can access the overlay with it only freezing every now and then.

[Conzar]

I have had this issue for a long time. Ubuntu 12.01, 13.10, and 14.04.all with an nvidia card (560 gtx). Its still a problem.

[terzag]

People having the issue: could you please add your voice on the Awesomenauts forum (see thread url above)?

[Plagman]

Does the issue only happen during online gameplay or is it reproducible from eg. the main menu?

[davad]

I've had it happen during gamemplay and while in the main menu.

[terzag]

It happens also on the main menu. As soon as you open the Steam overlay after launching the game, it randomly crashes.

BTW, it seems that I didn't say it there (the report on the game's forum is more complete) but I managed to reproduce the bug with Mesa/RadeonSi too. At first, I thought it happened only with Catalyst but that's not the case. It happened far more faster with Catalyst last time I checked, though.

[Plagman]

Can you see if the crash causes a new minidump file to be written out into /tmp/dumps?

[terzag]

Just tried a session but have been unable to crash the game. Currently using Mesa and can't use Catalyst currently on Ubuntu 14.10 (which would have done a better test). But in the past, it rarely crashed with Mesa, so I can't be sure that it's been fixed by an update. Will ask the devs if they addressed the issue or if it's a coincidence and will try again later.

[davad]

I was just able to get it to lock up in gameplay but not in the menu. Since it's always been a little random, I don't know if that means it wouldn't freeze up in the menu or didn't.

1. Started a practice game
2. Shift-Tab to bring up overlay
3. Clicked around for a couple seconds
4. Game unresponsive
5. Ctrl-Alt-F1 to change to a virtual terminal 6 kill -9 to kill Awesomenauts

There are some files in /tmp/dumps. Would killing Awesomenauts the way I did make a crashlog? What should I do with the files? Anything I should anonymize in them?

[terzag]

Oh, another thing that I forgot to mention here: it seemed at some point that the game didn't crash when being offline in Steam status (not full offline mode, only offline status). So, it looked like the issue was linked to the friend list (which is not displayed in offline status, I think?). Not sure it was a strong lead as the other people that were reporting the problem on the game's forum at the time never replyed after this.

Also, I had recorded a video on july that shows the problem: https://www.youtube.com/watch?v=aAHaB00lvdg As you can see, on the main menu that one time, I could open/close the overlay once, then it freezed when trying to reopening it a second time (had to kill the process).

[vrockai]

still an issue

[xplt]

I think this is game's issue: Awesomenauts is the only game on my Ubuntu, which has problems with the Overlay but developers at Ronimo don't listen :-/

[joaoglibras]

Same issue here, it's a Game problem, Ronimo says it's a steam problem, but they are wrong, because it happens only in Awesomenauts