Re: Memory Problem

form (mform) which calls other forms (oform). Actually, the mform
doesn't call the oform directly,
Right. It can't.

it creates a new thread where the
oform is created and called.
I don't understand what that means how this is possible. You'll need to
explain this some more.

When the oform is closed its thread is
set to nothing, but the oform's memory remains.
It's got a root. That's the long and short of it. First let's deal with your
design, fixing the leak should be easy after the design is explained.

--
Regards,
Alvin Bruney
------------------------------------------------------
Shameless author plug
Excel Services for .NET is coming...
https://www.microsoft.com/MSPress/books/10933.aspx
OWC Black Book www.lulu.com/owc
Professional VSTO 2005 - Wrox/Wiley


"javiers" <javier.scayola@xxxxxxxxx> wrote in message
news:1180011446.321191.225490@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
My VB.NET application is having a memory problem. It consist in a menu
form (mform) which calls other forms (oform). Actually, the mform
doesn't call the oform directly, When the oform is closed its thread is
set to nothing, but the oform's memory remains.

I'm using MemProfiler in order to know which objects are allocated in
memory. I've also used perfmon invoking the GC and I can see that the
memory keeps increasing. I thought that when the thread, which has
created the oform, is released the oform would be released too. But my
app don't behave like that.

Is it posible to create a thread that when is finished disposes all
its objects? What could be happening to my app?

Thanks in advance.



.

Loading