Has anyone seen System.Timers just stop working or go away. Its alomst like they get magically garbage collected. This behavior is easily seen in my program when running several instances of the same program. I typically get about 1/8 timers to just disapear!

Hi Greg,

This kind of questions have in this newsgroup a standard answer

"Show us some code?

Cor
> Has anyone seen System.Timers just stop working or go away. Its alomst
like they get magically garbage collected. This behavior is easily seen in
my program when running several instances of the same program. I typically
get about 1/8 timers to just disapear!
>
>

* "=?Utf-8?B?R3JlZw==?=" <(E-Mail Removed)> scripsit:
> Has anyone seen System.Timers just stop working or go away. Its
> alomst like they get magically garbage collected. This behavior is
> easily seen in my program when running several instances of the same
> program. I typically get about 1/8 timers to just disapear!

How many timers do you use?
Did you have a look at the CPU usage of the applications?
What do you mean by "go away"? They don't fire any more?

--
Herfried K. Wagner [MVP]
<http://www.mvps.org/dotnet>

I have one of these system timers in each app. I had about 3 other timers in the app as well (wich I have removed and replaced with other means

It seems things really start falling appart when I run about 40 instances of the application

Hard to tell if its CPU Usage related. Over time, the timers stop firing just with one application running. It just becomes more evident when I fire off about 40 or so applications.