Click here to Skip to main content
11,928,754 members (42,324 online)
Rate this:
Please Sign up or sign in to vote.
See more: C# Forms
Hi experts,

in an application, I have an object that contains a System.Timers.Timer[^]. The object is instantiated by Assembly.CreateInstance(string)[^], some properties are read and then there's no further need for the object.

Until recently, I observed no problem. The new thing is this object with a timer. Long after this objects intended lifespan, it keeps elapsing (and therefore executing methods, which it shouldn't).

What can I do to get rid of the object after all relevant properties have been read?
Is implementing the IDisposable[^] interface the way to go?
Posted 4-Jul-13 1:36am
Sushil Mate 4-Jul-13 6:57am
can't you disable your timer after read?

1 solution

Rate this: bad
Please Sign up or sign in to vote.

Solution 1

As Sushil Mate[^] already said in his comment[^] above. Disable the timer when you're done with the object.
If you're unsure about why the object is still alive even after it has gone out of scope. You'll find debugging/analyzing the heap an insightful endeavor. Current "state of the art" profilers usually have of these memory/heap analyzers "on board".

— Manfred

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

  Print Answers RSS
Top Experts
Last 24hrsThis month

Advertise | Privacy | Mobile
Web04 | 2.8.151126.1 | Last Updated 4 Jul 2013
Copyright © CodeProject, 1999-2015
All Rights Reserved. Terms of Service
Layout: fixed | fluid

CodeProject, 503-250 Ferrand Drive Toronto Ontario, M3C 3G8 Canada +1 416-849-8900 x 100