Home/ Questions/Q 8082925
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-05T17:16:58+00:00

There is a memory leak in a legacy application, so I don’t know the

  • 0

There is a memory leak in a legacy application, so I don’t know the code very well. I analyzed with MemProfiler and found out that a growing number of objects is referenced by TimerCall objects. These TimerCallbacks are referenced by _TimerCallback objects and these are children of the root. The graph looks like Root -> _TimerCallback -> TimerCallback -> MyObject.

Since MyObject needs a TimerCallback in its constructor there are several calls like:

new MyObject(int timeout, new TimerCallback(SomeCallbackMethod));

To be honest it looks quite awkward to me to do it like this, but as I wrote it’s a legacy application and it was written in “C style” C#, with lots of null assignments and Dispose() calls …

So how can I remove these references to TimerCallback from root?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    This looks like your TimerCallback is being used in a Timer object. Find out, why there are a lot of Timers active. They are likely to be the real roots keeping your callback alive.

    I was just looking around the _TimerCallback class in Reflector and although I don’t fully comprehend what’s going on I think this class is a red herring. I think the root cause are Timers (maybe even disabled ones).

    • 0