Collisions and sleep

[EmperorPenguin18]

Even though I never touch any sleep functions, when I run cpSpaceStep() after a collision, and it gets to line 223 of cpSpaceComponent.c which is this;

cpBool sleep = (space->sleepTimeThreshold != INFINITY);

somehow it gets set to 1. I've double checked and sleepTimeThreshold is infinity at this point.

The reason this is an issue at all is because later on during this Step it gets stuck in an infinite loop looking for arbiters. What's curious about this issue is it only happens for me when I do a Release build in cmake and then link statically. It also doesn't happen on Windows, just Linux and emscripten from my testing.

[flychscake]

Seems to occur only if built on gcc with --ffast-math in CFLAGS, specifically -ffinite-math-only optimization appears to be the cause.