Presumably it works with valgrind because it prevents the fatal effect of the
bad memory access which causes the problem. Note that valgrind stopped logging
errors after 1000 instances of the same (presumably harmless) issue in the
Awesomenauts code. Maybe there's some way to suppress those, so we can see the
problem?