Re: [racket-users] More Racket Place abuse^H^H^H^H^H issues

2015-09-03 Thread Matthew Flatt
At Thu, 3 Sep 2015 11:12:50 +0100, Tim Brown wrote: > On 28/08/15 20:02, Matthew Flatt wrote: > > 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

Re: [racket-users] More Racket Place abuse^H^H^H^H^H issues

2015-09-03 Thread Tim Brown
On 28/08/15 20:02, Matthew Flatt wrote: > 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 a

Re: [racket-users] More Racket Place abuse^H^H^H^H^H issues

2015-08-31 Thread Tim Brown
Matthew, Thanks again. That wasn't the cleanest bug report, and I was really hoping it wasn't attibutable to some flaky library software on my system (especially since *I* needed PostgreSQL to trigger it). Again, many thanks for working on and fixing the bug. I'm away from work at the moment, bu

Re: [racket-users] More Racket Place abuse^H^H^H^H^H issues

2015-08-28 Thread Matthew Flatt
I don't think my guess was right. Happily, my accounting-related test is like yours in that it passes place channels over place channels. Further testing with that example provoked symptoms more like the ones you describe. The bug: If a GC happens after a thread receives the message but before it

Re: [racket-users] More Racket Place abuse^H^H^H^H^H issues

2015-08-28 Thread Matthew Flatt
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

[racket-users] More Racket Place abuse^H^H^H^H^H issues

2015-08-28 Thread Tim Brown
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.

[racket-users] More Racket Place abuse^H^H^H^H^H issues

2015-08-24 Thread Tim Brown
Hello all, I now have a new problem with places. This time, it has to do with the interaction of places, sandboxes, threads and PostgreSQL. I promise I’m not actively looking for ways to break Racket, and that this is as simple as I have been able to make a reproducible error (although I’m also t