My VB.NET 2003 application sometimes remains in memory, verified by Task
Manager.

I know the app must be keeping a reference to something, but how do I find
out what?

Is there a tool/technique to determine what this reference may be?

Thanks

"Michael Jackson" <(E-Mail Removed)> wrote in message
news:%%tdf.5060$om5.2680@dukeread04...
> My VB.NET 2003 application sometimes remains in memory, verified by Task
> Manager.
>
> I know the app must be keeping a reference to something, but how do I find
> out what?
>
> Is there a tool/technique to determine what this reference may be?
>
> Thanks
>
Make sure your auxiliary threads (if any) are Background threads, else your
process will stay resident when such thread did not terminate when the Main
threads exits.

Willy.

I've created no threads, so I assume that would not be the problem.

Short of stepping thru code, etc, I guess I need to purchase a profiler of
some sort.

Michael


"Willy Denoyette [MVP]" <(E-Mail Removed)> wrote in message
news:eTVdf%(E-Mail Removed)...
>
> "Michael Jackson" <(E-Mail Removed)> wrote in message
> news:%%tdf.5060$om5.2680@dukeread04...
>> My VB.NET 2003 application sometimes remains in memory, verified by Task
>> Manager.
>>
>> I know the app must be keeping a reference to something, but how do I
>> find out what?
>>
>> Is there a tool/technique to determine what this reference may be?
>>
>> Thanks
>>
> Make sure your auxiliary threads (if any) are Background threads, else
> your process will stay resident when such thread did not terminate when
> the Main threads exits.
>
> Willy.
>

Great name you have there Michael, I assume it is an assumed name?, if not
it must have caused much mirth during your lifetime.

--
Best Regards

The Inimitable Mr Newbie º¿º


"Michael Jackson" <(E-Mail Removed)> wrote in message
news:NTydf.5088$om5.2263@dukeread04...
> I've created no threads, so I assume that would not be the problem.
>
> Short of stepping thru code, etc, I guess I need to purchase a profiler of
> some sort.
>
> Michael
>
>
> "Willy Denoyette [MVP]" <(E-Mail Removed)> wrote in message
> news:eTVdf%(E-Mail Removed)...
>>
>> "Michael Jackson" <(E-Mail Removed)> wrote in message
>> news:%%tdf.5060$om5.2680@dukeread04...
>>> My VB.NET 2003 application sometimes remains in memory, verified by Task
>>> Manager.
>>>
>>> I know the app must be keeping a reference to something, but how do I
>>> find out what?
>>>
>>> Is there a tool/technique to determine what this reference may be?
>>>
>>> Thanks
>>>
>> Make sure your auxiliary threads (if any) are Background threads, else
>> your process will stay resident when such thread did not terminate when
>> the Main threads exits.
>>
>> Willy.
>>
>
>

Michael Jackson wrote:
> I've created no threads, so I assume that would not be the problem.
>
> Short of stepping thru code, etc, I guess I need to purchase a
> profiler of some sort.

You've not explained what type of application this is. It does make a
big difference.

For example the following code will exhibit the behaviour you describe:

class MyForm : Form
{
static void Main()
{
MyForm form = new MyForm();
form.Visible = true;
Application.Run();
}
}

Richard
--
http://www.grimes.demon.co.uk/workshops/fusionWS.htm
http://www.grimes.demon.co.uk/workshops/securityWS.htm

What kind of application is it (Windows or Console like)? Keep in mind that
threads might be created under control of the framework (no managed
application is single threaded), for instance timers might fire on
threadpool threads (though these are Background threads), the process won't
go away when such thread does a blocking call into unmanaged code.

Willy.

"Michael Jackson" <(E-Mail Removed)> wrote in message
news:NTydf.5088$om5.2263@dukeread04...
> I've created no threads, so I assume that would not be the problem.
>
> Short of stepping thru code, etc, I guess I need to purchase a profiler of
> some sort.
>
> Michael
>
>
> "Willy Denoyette [MVP]" <(E-Mail Removed)> wrote in message
> news:eTVdf%(E-Mail Removed)...
>>
>> "Michael Jackson" <(E-Mail Removed)> wrote in message
>> news:%%tdf.5060$om5.2680@dukeread04...
>>> My VB.NET 2003 application sometimes remains in memory, verified by Task
>>> Manager.
>>>
>>> I know the app must be keeping a reference to something, but how do I
>>> find out what?
>>>
>>> Is there a tool/technique to determine what this reference may be?
>>>
>>> Thanks
>>>
>> Make sure your auxiliary threads (if any) are Background threads, else
>> your process will stay resident when such thread did not terminate when
>> the Main threads exits.
>>
>> Willy.
>>
>
>

that means it's still running!
perhaps you just hide the main windows instead of closing it?

"Michael Jackson" <(E-Mail Removed)> wrote in message
news:%%tdf.5060$om5.2680@dukeread04...
> My VB.NET 2003 application sometimes remains in memory, verified by Task
> Manager.
>
> I know the app must be keeping a reference to something, but how do I find
> out what?
>
> Is there a tool/technique to determine what this reference may be?
>
> Thanks
>