As I mentioned earlier, Google Chrome has this government-issued component that does nothing but write a log for Google—it drops the log in the “current directory” before doing anything else.

According to this statement, the fix for this bug is only expected to land in Chrome 29. So what do we do until then?

Someone has come up with a fix that seems quite useful

In the mean time you can edit /opt/google/chrome/google-chrome and add "cd /tmp", before the last line 'exec -a "$0" "HERE/chrome""HERE/chrome" "@"'

The basic idea is to edit the Google Chrome launcher script and cd /tmp before the actual launch. Because that setting adds a log under the “current directory (CWD)”, the log ends up being thrown into /tmp. Anyway, it’s just junk.

Thanks again to Alian, the author of this fix.