t
Sent: Wednesday, March 30, 2016 2:06 AM
To: Rodrigo Kumpera <kump...@gmail.com<mailto:kump...@gmail.com>>
Cc: Straw, David (Storage) <david.st...@hpe.com<mailto:david.st...@hpe.com>>;
mono-devel-list@lists.ximian.com<mailto:mono-devel-list@lists.ximian.com>
Subject: Re: [M
To: Rodrigo Kumpera <kump...@gmail.com>
Cc: Straw, David (Storage) <david.st...@hpe.com>;
mono-devel-list@lists.ximian.com
Subject: Re: [Mono-dev] Using valgrind with Mono
Unfortunately, PR 2783 did not have any noticeable effect. We still see
thousands of leaks like the following:
o-devel-list@lists.ximian.com
Subject: Re: [Mono-dev] Using valgrind with Mono
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: Tuesd
com>
Cc: Straw, David (Storage) <david.st...@hpe.com>;
mono-devel-list@lists.ximian.com
Subject: Re: [Mono-dev] Using valgrind with Mono
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, 2
devel-list-boun...@lists.ximian.com] *On Behalf Of *Zinkevicius, Matt
> *Sent:* Monday, March 28, 2016 2:42 PM
> *To:* Rodrigo Kumpera <kump...@gmail.com>
>
> *Cc:* Straw, David (Storage) <david.st...@hpe.com>;
> mono-devel-list@lists.ximian.com
> *Subject:
: Monday, March 28, 2016 2:42 PM
To: Rodrigo Kumpera <kump...@gmail.com>
Cc: Straw, David (Storage) <david.st...@hpe.com>;
mono-devel-list@lists.ximian.com
Subject: Re: [Mono-dev] Using valgrind with Mono
Hi Rodrigo,
I am not finding a recent commit in master that mentions
“mono_metho
<matt.zinkevic...@hpe.com>
Cc: Zoltan Varga <var...@gmail.com>; Straw, David (Storage)
<david.st...@hpe.com>; mono-devel-list@lists.ximian.com
Subject: Re: [Mono-dev] Using valgrind with Mono
The memory leak on mono_method_get_header was recently fixed in master.
On Mon, Mar 2
gt;
> *Cc:* Straw, David (Storage) <david.st...@hpe.com>;
> mono-devel-list@lists.ximian.com
>
> *Subject:* Re: [Mono-dev] Using valgrind with Mono
>
>
>
> Hi Zoltan,
>
>
>
> Thank you for investigating my findings. I will apply the fix you linked
> to and report b
var...@gmail.com>
Cc: Straw, David (Storage) <david.st...@hpe.com>;
mono-devel-list@lists.ximian.com
Subject: Re: [Mono-dev] Using valgrind with Mono
Hi Zoltan,
Thank you for investigating my findings. I will apply the fix you linked to and
report back. While I understand the other lea
Varga [mailto:var...@gmail.com]
Sent: Sunday, March 27, 2016 4:45 PM
To: Zinkevicius, Matt <matt.zinkevic...@hpe.com>
Cc: mono-devel-list@lists.ximian.com; Straw, David (Storage)
<david.st...@hpe.com>
Subject: Re: [Mono-dev] Using valgrind with Mono
Hi,
Fixed the last one in:
https:
Hi,
Fixed the last one in:
https://github.com/mono/mono/commit/b97ac0023256bf7d915552f5f24a7742b28c32b7
The first two are leaks, but they should be small and bounded. Will look
into fixing them to decrease the noise.
Zoltan
On Sun, Mar 27, 2016 at 6:23 PM, Zinkevicius, Matt
Hello,
Our backend service running on Mono 4.2.2 on Linux is experiencing an unmanaged
memory leak. When running our stress tests for several hours, we see the
managed heap sit around 50 MB, while private memory keeps growing until the
process is killed because of OOM. I am therefore
12 matches
Mail list logo
