Unfortunately, PR 2783 did not have any noticeable effect. We still see
thousands of leaks like the following:
==12142== 89,860 (89,704 direct, 156 indirect) bytes in 2,800 blocks are
definitely lost in loss record 19,763 of 19,792
==12142==at 0x4C26FEF: calloc (vg_replace_malloc.c:711)
Thanks, Rodrigo!
I’ve ported this to 4.2 to test, though these changes seem to only address AOT,
and we’re seeing this leak using the normal JIT runtime.
Matt
From: Rodrigo Kumpera [mailto:kump...@gmail.com]
Sent: Tuesday, March 29, 2016 6:15 PM
To: Zinkevicius, Matt
This is the PR in question: https://github.com/mono/mono/pull/2783
It probably won't make into 4.2, but should definitely be in 4.4.
On Tue, Mar 29, 2016 at 11:55 AM, Zinkevicius, Matt <
matt.zinkevic...@hpe.com> wrote:
> Hi Rodrigo,
>
>
>
> Is the following the PR that you were referring to
Why not just include references to Mono.Posix.dll in the Windows build? You
don't have to install the full framework. We have a similar issue with server
apps that are developed on Windows and run on Linux. We just put a win32 build
of Mono into our source tree and added Mono.Posix as a
Hi Rodrigo,
Is the following the PR that you were referring to that fixes the
“mono_method_get_header” leak?
https://github.com/mono/mono/pull/2705
I am eager to find it, as this particular leak seems to be the most egregious
of the ones we’re experiencing, in terms of both occurrences and
> From: mono-devel-list-boun...@lists.ximian.com [mailto:mono-devel-list-
> boun...@lists.ximian.com] On Behalf Of Greg Young
>
>
(for clarification of my previous response, because I was asked for
clarification off-list)
If you have some code that calls Mono.Posix.Something(), and you have a