Title: Leak in System.Timers.Timer?
I'm seeing what looks like a memory leak somewhere in System.Timers.Timer. I'm using mono 1.1.4 on a linux system. The code I used to reproduce the problem is:
--
using System;
namespace TimerTest
{
public class TimerTest
{
Looks to me like your creating timers in an infinite loop wich would of course continue to consume resources
while(true) { InitTimeout(ref timeout); System.Threading.Thread.Sleep(10); }
true will always be true so you are spinning off a lot of timers ri
Oh, wait I see you are passing the same one by ref and setting it to null. Do you get different behaviour under windows? Joe Audette <[EMAIL PROTECTED]> wrote:
Looks to me like your creating timers in an infinite loop wich would of course continue to consume resources
while(true) {
Could it be the "lapsed listener problem"?
http://www.andymcm.com/dotnetfaq.htm#5.8Brian Kroeker <[EMAIL PROTECTED]> wrote:
I'm seeing what looks like a memory leak somewhere in System.Timers.Timer. I'm using mono 1.1.4 on a linux system. The code I used to reproduce the problem is:
-
h 10, 2005 12:03 PMTo:
mono-devel-list@lists.ximian.comSubject: Re: [Mono-devel-list] Leak
in System.Timers.Timer?
Oh, wait I see you are passing the same one by ref and setting it to
null. Do you get different behaviour under windows? Joe Audette
<[EMAIL PROTECTED]> wrote:
L
e event went away.
>
> Brian
>
>
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]
> Sent: Thursday, March 10, 2005 12:03 PM
> To: mono-devel-list@lists.ximian.com
> Subject: Re: [Mono-devel-list] Leak in System.Timers.Timer?
&
Title: RE: [Mono-devel-list] Leak in System.Timers.Timer?
The test code I posted creates way more timers than I would in my actual code - so that the symptoms can be seem more readily. Perhaps this is not a valid test if the code produces objects faster than the gc collects them. I did run
