I'll add a lock at lines 1092-1096 of "newgc.c", and we'll see if that
should I open the issue or will you do it? (Speaking of race conditions...).
I'll re-run the tests with the lock once it is in the repo - sometimes
it takes hours for this bug to exhibit and with 8 HTs the process in
question consumes slightly more than 500% of CPU time - which means the
computer sounds it's going to take off and fly. I'll keep it up and
running overnight again.
And thank you for the explanation, digging in Racket internals has a
very varying degree of difficulty :)
You received this message because you are subscribed to the Google Groups "Racket
To unsubscribe from this group and stop receiving emails from it, send an email
To view this discussion on the web visit