/tmp/gameoverlayrenderer.log grows huge extremely fast and fills tmpfs

steamclosed reviewedoverlay

ValveSoftware/steam-for-linux#3623 · opened 2014-12-08 by rpdelaney · updated 2014-12-23 · 4 comments · github

Rrpdelaney 2014-12-08 github

When I'm playing the Linux version of Transistor (app/237930), /tmp/gameoverlayrenderer.log becomes enormous after a few minutes of gameplay. After a few minutes more it is a full 4gb in size and tmpfs is full, which causes all kinds of problems elsewhere in the system. I have not yet observed this problem with other apps.

It appears that the log is being spammed with the same error, for example:

Mon Dec 08 02:49:05 2014 UTC - Track win 0x240000b cursor 0x240000e

I ran xz on an 800mb gameoverlayrenderer.log and the compressed file is 124kb, which supports the theory that the data are close to uniform. A hackish work-around I've been using is:

$ while sleep 15; do >/tmp/gameoverlayrenderer.log; done

But obviously, it would be better if I didn't have to remember to do this before loading the game.

IindriApollo 2014-12-09 github

I also have this strange behavior where I get a 65 mb gameoverlayrenderer.log filled with :
mar déc 09 14:35:55 2014 UTC - Track win 0x380000b cursor 0x380000e
in less than a second.

Rrpdelaney 2014-12-09 github

@indriApollo also in Transistor or another app?

IindriApollo 2014-12-10 github

@rpdelaney yes (in transistor)

PPlagman 2014-12-11 github

Will be fixed in next Beta cycle.

Nothing extracted yet.