Done, thanks.
https://github.com/rakudo/rakudo/issues/1440
On Mon, Jan 22, 2018 at 4:14 PM, Elizabeth Mattijsen wrote:
> This feels like a bug to me. So please make report this as a potential
> issue, either by mailing rakudo...@perl.org, or by creating an issue on
> http://github.com/rakudo/r
This feels like a bug to me. So please make report this as a potential issue,
either by mailing rakudo...@perl.org, or by creating an issue on
http://github.com/rakudo/rakudo .
Thank you!
> On 22 Jan 2018, at 01:24, David E. wrote:
>
> I'm not certain where to report this (ie: rakudo vs Moar
It looks like the String may not be at fault - changing the argument to an
int32 pointer results in the same memory leak. In either case, the
variable is allocated on the static in the C function and would be
automatically freed when the function returns, so the problem has to be
some temporary at
I believe that this is actually a result of Perl 6 delegating responsibility of
memory management for arguments passed to callbacks from native code to the
native code.
I wonder if the issue is that you're sending a constant which is being
reallocated and recreated and never cleared out from th
I'm not certain where to report this (ie: rakudo vs MoarVM), so I'm
starting here.
After some experimentation, I finally traced down a segfault I've been
getting to a memory leak in the NativeCall interface. I'm using it to
facilitate testing of a 32-bit embedded (meaning no dynamic allocation) C
