On Thursday, 7 April 2016 at 04:36:02 UTC, Yuxuan Shui wrote:
> On Thursday, 7 April 2016 at 04:24:48 UTC, Yuxuan Shui wrote:
>> [...]
>
> Looks like _d_arrayappendcTX asked for a enormous amount of memory and it fails, can't figure out why

Just find out it's my own fault.

BTW, memory block allocated by core.stdc.stdlib.malloc will not be scanned by collector, right?

On Thursday, 7 April 2016 at 05:23:47 UTC, Yuxuan Shui wrote:
> On Thursday, 7 April 2016 at 04:36:02 UTC, Yuxuan Shui wrote:
>> On Thursday, 7 April 2016 at 04:24:48 UTC, Yuxuan Shui wrote:
>>> [...]
>>
>> Looks like _d_arrayappendcTX asked for a enormous amount of memory and it fails, can't figure out why
>
> Just find out it's my own fault.
>
> BTW, memory block allocated by core.stdc.stdlib.malloc will not be scanned by collector, right?

right, that's why it's annotated @nogc ;)

On 07/04/2016 5:23 PM, Yuxuan Shui wrote:
> On Thursday, 7 April 2016 at 04:36:02 UTC, Yuxuan Shui wrote:
>> On Thursday, 7 April 2016 at 04:24:48 UTC, Yuxuan Shui wrote:
>>> [...]
>>
>> Looks like _d_arrayappendcTX asked for a enormous amount of memory and
>> it fails, can't figure out why
>
> Just find out it's my own fault.
>
> BTW, memory block allocated by core.stdc.stdlib.malloc will not be
> scanned by collector, right?

Unless you add it, no.