Re: [Mono-dev] [Mono-gc-list] Mono memory problems!

2007-07-24 Thread Jonathan Gagnon
À : David Wolinsky Cc : Andreas Färber; Peer-to-peer networking group discussions; [EMAIL PROTECTED]; mono-devel Objet : Re: [Mono-dev] [Mono-gc-list] Mono memory problems! Hello folks, Thanks for tracking this problem down. Thanks for pointing out the comment in the source code; I went

Re: [Mono-dev] [Mono-gc-list] Mono memory problems!

2007-07-24 Thread Paolo Molaro
On 07/24/07 Jonathan Gagnon wrote: I'm pretty sure that this will fix bug #81727 that I filed a few months ago, although I don't have time to test it for the moment. Thanks, confirmed that issue is fixed as well. lupus -- -

Re: [Mono-dev] [Mono-gc-list] Mono memory problems!

2007-07-18 Thread David Wolinsky
We've isolated the problem down to AutoResetEvent... using System; using System.Threading; namespace Ipop { public class IPOP_Common { public static void Main() { AutoResetEvent re = null; while(true) { re = new AutoResetEvent(false); re.Close(); } }

Re: [Mono-dev] [Mono-gc-list] Mono memory problems!

2007-07-18 Thread David Wolinsky
FYI, this case is only triggered when using gmcs and not mcs. David David Wolinsky wrote: We've isolated the problem down to AutoResetEvent... using System; using System.Threading; namespace Ipop { public class IPOP_Common { public static void Main() { AutoResetEvent re = null;

Re: [Mono-dev] [Mono-gc-list] Mono memory problems!

2007-07-18 Thread Alan McGovern
Drop a bug report to: bugzilla.ximian.com containing that testcase and put it under the 'compilers' section. It sounds like a gmcs issue. Alan. On 7/18/07, David Wolinsky [EMAIL PROTECTED] wrote: FYI, this case is only triggered when using gmcs and not mcs. David David Wolinsky wrote:

Re: [Mono-dev] [Mono-gc-list] Mono memory problems!

2007-07-18 Thread Robert Jordan
Alan McGovern wrote: Drop a bug report to: bugzilla.ximian.com containing that testcase and put it under the 'compilers' section. It sounds like a gmcs issue. That's rather a NET_2_0 issue. AutoResetEvent has a different implementation under 2.0. Robert Alan. On 7/18/07, David Wolinsky

Re: [Mono-dev] [Mono-gc-list] Mono memory problems!

2007-07-18 Thread Cedric Vivier
On 7/18/07, Robert Jordan [EMAIL PROTECTED] wrote: Alan McGovern wrote: Drop a bug report to: bugzilla.ximian.com containing that testcase and put it under the 'compilers' section. It sounds like a gmcs issue. That's rather a NET_2_0 issue. AutoResetEvent has a different implementation

Re: [Mono-dev] [Mono-gc-list] Mono memory problems!

2007-07-18 Thread Cedric Vivier
On 7/18/07, Cedric Vivier [EMAIL PROTECTED] wrote: Looks like the _wapi_private_handles array expands indefinitely but never shrinks. Hmm, by shrinks I meant the allocated slots are not reused like they should because of the Close() I guess. ___

Re: [Mono-dev] [Mono-gc-list] Mono memory problems!

2007-07-18 Thread Miguel de Icaza
namespace Ipop { public class IPOP_Common { public static void Main() { AutoResetEvent re = null; while(true) { re = new AutoResetEvent(false); re.Close(); } } } } blows up memory That depends on the finalizer to run to release memory

Re: [Mono-dev] [Mono-gc-list] Mono memory problems!

2007-07-18 Thread David Wolinsky
That case leaks as well. Regards, David Miguel de Icaza wrote: namespace Ipop { public class IPOP_Common { public static void Main() { AutoResetEvent re = null; while(true) { re = new AutoResetEvent(false); re.Close(); } } } } blows up

Re: [Mono-dev] [Mono-gc-list] Mono memory problems!

2007-07-18 Thread Andreas Färber
Am 18.07.2007 um 19:54 schrieb David Wolinsky: That case leaks as well. Regards, David Miguel de Icaza wrote: re = new AutoResetEvent(false); re.Close(); That depends on the finalizer to run to release memory from the unmanaged side, since AutoResetEvent implements

Re: [Mono-dev] [Mono-gc-list] Mono memory problems!

2007-07-18 Thread David Wolinsky
In fact, I was able to fix the problem. For some reason in WaitHandle.cs, the line... safe_wait_handle = new SafeWaitHandle (value, false); should be... safe_wait_handle = new SafeWaitHandle (value, true); (at least it makes sense according to other docs I read)... second... in

Re: [Mono-dev] [Mono-gc-list] Mono memory problems!

2007-07-18 Thread Cedric Vivier
On 7/18/07, I wrote : Looks like the _wapi_private_handles array expands indefinitely but never shrinks. Hmm, by shrinks I meant the allocated slots are not reused like they should because of the Close() I guess. I've continued my investigation from the low-level handles.c to the managed.

Re: [Mono-dev] [Mono-gc-list] Mono memory problems!

2007-07-18 Thread David Wolinsky
Bugzilla report and patch Regards, David http://bugzilla.ximian.com/show_bug.cgi?id=82134 ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list

Re: [Mono-dev] [Mono-gc-list] Mono memory problems!

2007-07-18 Thread Miguel de Icaza
Hello folks, Thanks for tracking this problem down. Thanks for pointing out the comment in the source code; I went and re-read the documentation and I clearly did not understand it the first time over, because the leak was documented to happen only in the .NET 1.0 and 1.1 scenarios, not

Re: [Mono-dev] [Mono-gc-list] Mono memory problems!

2007-07-18 Thread Miguel de Icaza
second... in SafeWaitHandle.cs, the line ... NativeEventCalls.CloseEvent_internal (DangerousGetHandle()); should be... NativeEventCalls.CloseEvent_internal (handle); I missed this one, I have now applied this as well. Miguel