Well, that was a difficult one to track down, but easy to fix: https://github.com/racket/racket/commit/a484cd76e57001cfb52b5791b66b6df508121cef

Bugs that cause the scheduler to go wrong are always tricky to pull apart. The ones where place-level concurrency breaks Racket-level concurrency are even trickier.