[racket-dev] BUG: busy-waiting

Confirm, I'm having a very similar issue. I haven't run gdb yet but I would bet several horses on my code running through scheme_block_until near the busy wait.

I will try to get a minimal example together after I get out of meetings for the day.

Cheers

> On Sep 3, 2014, at 16:52, Jan Dvořák <mordae at anilinux.org> wrote:
> 
> Hello,
> 
> I am hitting a rather uncomfortable bug that causes runtime to start internal busy-waiting at around:
> 
> #0  scheme_block_until(_f=<syncing_ready>, fdf=<scheme_syncing_needs_wakeup>)
>   at ../src/thread.c:5199
> #1  do_sync (name="sync", with_break=0, with_timeout=0)
>   at ../src/thread.c:7109
> 
> It goes through ../src/thread.c:5190, which Matthew mentions in one of his recent patches.
> 
> The code that manages to trigger this have been written under NDA and cannot be published. I have not yet managed to reproduce the issue separately, but it seems that this might not be the only instance:
> 
>   (09:28:36 PM) m4burns: Mordae: I'm having a similar problem somewhere in
>                          `inflate`. Haven't applied a debugger yet, but
>                          there's certainly no busy waiting in the script.
> 
> I am stuck and would like to ask for your help.
> 
> Best regards,
> Jan Dvorak
> 
> 
> 
> _________________________
> Racket Developers list:
> http://lists.racket-lang.org/dev
>