I haven't been able to replicate the specific crash, but I have a guess at the problem.
I think the sandbox is relevant because `sandbox-memory-limit` remains in effect (even though you're disabling the per-evaluation limit by setting `sandbox-eval-limits`). A sandbox memory limit triggers memory accounting in the GC. I see that memory accounting in the GC has a problem with places, and I can provoke a crash by targeting that problem directly. I'll fix that problem, and hopefully it will fix the crash you're seeing. At Fri, 28 Aug 2015 06:55:51 -0700 (PDT), Tim Brown wrote: > Has anyone had the chance to look at, or been able to reproduce this? > > Tim > > -- > You received this message because you are subscribed to the Google Groups > "Racket Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email > to racket-users+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
