thread is blocked unexpectly about chezscheme

[yjqww6]

I tested it on 64-bit Linux, the code work as expected and didn't block.

[dybvig]

I believe the problem is that the WIN32 definition of s_ee_read_char in expeditor.c is not deactivating the thread before calling (and possibly blocking on) ReadConsoleInput. When the background thread, which is busily creating and dropping bignums once i gets out of fixnum range, detects it's time to do a collection, the blocked but still active main thread prevents the collection from occurring, effectively blocking the background thread as well. You can verify this is the problem by setting collect-notify to #t and seeing if collections stop after a while. Or you can go ahead and insert calls to deactivate_thread and reactivate_thread around the call to ReadConsoleInput (following the pattern in the non-WIN32 definition of s_ee_read_char) and see if that fixes the problem.

In the 64-bit version, i wouldn't have exceeded the fixnum range in your test (assuming no time travel), so no bignums were allocated, and no collections were needed.

[yjqww6]

@dybvig I have modified the code according to your words and recompiled it, and it seems the problem do not occurs anymore.