18:22:51jsnellI would have guessed it was another of those cases of system calls actually working properly on OS X
18:24:34nyefstassats: IIRC, the memory requirement for futexes is a single (unboxed?) word, plus possibly kernel memory overhead /while they are being slept on/.
18:25:50stassatsi think ccl just uses pthread_mutex
18:26:34stassatsi think pthreads are reasonable exercised to actually work on darwin
18:26:42nyefSo no foreign objects to track that can leak, for example. A winapi mutex is represented by a HANDLE, but it's tied to some kernel state that can leak.
18:27:15stassatsfinalizers to the rescue (if you're lucky)
18:27:43nyefIf you're looking to finalizers to save you, you're *already* out of luck.
18:27:43jsnellwe had special support for pthread mutexes in the gc
18:29:02stassatsi don't expect mutexes becoming garbage all that often
18:30:41jsnellI'm trying to remember whether that special support was anything except custom finalizer machinery. probably not
18:33:56stassatsthe way we use select is also bad on non-linux
18:47:17stassatsi guess i'll just have to try using pthreads and see what happens