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 accounting in the GC has a
> problem with places, and I can provoke a crash by targeting that
> problem directly.
Out of interest - is there much overhead in having memory accounting
active in the GC?
I can’t avoid it, since I’ll be using sandboxes...
but is there any idea of the cost?
Tim
--
Tim Brown CEng MBCS <tim.br...@cityc.co.uk>
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
City Computing Limited · www.cityc.co.uk
City House · Sutton Park Rd · Sutton · Surrey · SM1 2AE · GB
T:+44 20 8770 2110 · F:+44 20 8770 2130
────────────────────────────────────────────────────────────────────────
City Computing Limited registered in London No:1767817.
Registered Office: City House, Sutton Park Road, Sutton, Surrey, SM1 2AE
VAT No: GB 918 4680 96
--
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.
