If the garbage collector is there to handle it, then, it sounds to me,
like it IS possible
The GC is not there to handle memory leaks: it's there to reclaim memory
which is no longer referenced anywhere in the program; a side effect of this
is you can't have memory leaks, because as soon as you have one, the GC will
reclaim that memory.
- I think I have a .Net component in my app, which has a memory leak
I need to know how to find this....
First of all, you should verify if that's *really* a memory leak, i.e. if
you're losing memory because you lost any track of it. In order to check
this, you should call GC.Collect() and see if your "lost" memory comes back:
if it does, then that actually was a memory leak, but you can handle it by
periodically invoking the GC this way.
If your memory doesn't come back even after calling the GC, then it's not
leaked: it must be referenced somewhere in the program, even if you may not
be aware of it; memory is not considered to be available if there is any
reference to it anywhere (maybe inside some really complex data structure
which made you forget it).
Massimo
