obstinate custom object

Question

0.00/5 (No votes)

See more:

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 0:36am

lukeer

Add a Solution

Comments

Sushil Mate 4-Jul-13 6:57am

can't you disable your timer after read?

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

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

Manfred Rudolf Bihy · Answer 1 · 2013-07-04T01:13:00

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".

Regards,

— Manfred