duncan.coutts:
> On Fri, 2009-06-26 at 13:00 +0100, Simon Marlow wrote:
>
> > Maybe bzlib allocates using malloc()? That would not be tracked by
> > GHC's memory management, but could cause OOM.
>
> Yes it does.
>
> > Another problem is that if you ask for a large amount of memory in one
> >
On Fri, 2009-06-26 at 13:00 +0100, Simon Marlow wrote:
> Maybe bzlib allocates using malloc()? That would not be tracked by
> GHC's memory management, but could cause OOM.
Yes it does.
> Another problem is that if you ask for a large amount of memory in one
> go, the request is usually honour
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
On 22/06/2009 23:48, Bulat Ziganshin wrote:
Hello Marcin,
Tuesday, June 23, 2009, 2:31:13 AM, you wrote:
Now this took an odd turn, because the simulation started crashing with
out-of-memory errors _after_ completing (during bz2 compression). I'm fairly
certain this is a GC/FFI bug, b
