Re: [MirageOS-devel] Out of memory

[Thomas Leonard <talex5@xxxxxxxxx>]

[ assuming this was intended for the list, so re-adding it ]

On 17 December 2015 at 17:08, David Sheets <kosmo.zb@xxxxxxxxx> wrote:
> On Thu, Dec 17, 2015 at 4:59 PM, Thomas Leonard <talex5@xxxxxxxxx> wrote:
>> I've been trying to track down some occasional out-of-memory errors
>> with my Mirage/Xen unikernel.
[...]
>> The C code in caml_ba_alloc does:
>>
>>     data = malloc(size);
>>     if (data == NULL && size != 0) caml_raise_out_of_memory();
>>
>> I guess we should do a GC.full_major here and retry, right? Should
>> this be changed upstream in OCaml itself?
>
> Cool. Looks like a bug. As a side note, I think you mean
> caml_check_urgent_gc instead of Gc.full_major.

Is this documented somewhere? Looking at the code, it just does:

  if (caml_force_major_slice) caml_minor_collection();

Is there any reason to think caml_force_major_slice will be set? I
have no idea how this all works...


-- 
Dr Thomas Leonard        http://roscidus.com/blog/
GPG: DA98 25AE CAD0 8975 7CDA  BD8E 0713 3F96 CA74 D8BA

_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@xxxxxxxxxxxxxxxxxxxx
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel