On Friday 26 June 2009, Simon Marlow wrote: > Maybe bzlib allocates using malloc()? That would not be tracked by > GHC's memory management, but could cause OOM.
probably, because it's a binding to a C library. I'm really busy right now, but I'll try and create a small program to repro this error. > Another problem is that if you ask for a large amount of memory in one > go, the request is usually honoured immediately, and then we GC shortly > afterward. If this is the problem for you, please submit a ticket and > I'll see whether it can be changed. You could work around it by calling > System.Mem.performGC just before allocating the memory. I've already worked around the problem. -- Marcin Kosiba
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Haskell-Cafe mailing list [email protected] http://www.haskell.org/mailman/listinfo/haskell-cafe
