App don't stop when closing the form

[ThunderMusic]

Hi,
My app does not stop whan I click on the form. I mean, the form is
closing, but the process keeps running in the task manager. So I figured
there are memory leaks or some object's process stuck at some point. Is
there an easy way to know where it comes from other than putting breakpoints
all over the code? 'cause it's huge and I would have to set breakpoints for
at least a day or two

thanks

[Josip Habjan]

Obviously you have wrong approach on creating and destroying objects
instances.
For all objects that have implemented IDisposable, i suggest you to call
obj.Dispose and set it to obj = Nothing (or null) when you dont need him any
more.

.... it is also possible that you did not exit some loop !?

Regards,
Josip Habjan
URL: http://www.habjansoftware.com


"ThunderMus ic" <NO*******@symp atico.caSPAMATA LL> wrote in message
news:OS******** *****@TK2MSFTNG P12.phx.gbl...

Hi,
My app does not stop whan I click on the form. I mean, the form is
closing, but the process keeps running in the task manager. So I figured
there are memory leaks or some object's process stuck at some point. Is
there an easy way to know where it comes from other than putting
breakpoints
all over the code? 'cause it's huge and I would have to set breakpoints
for
at least a day or two

thanks

[Cor Ligthert]

ThunderMusic,

What do you mean with keeps running, all day long or a short time?

Cor

[Cor Ligthert]

Josip,

For all objects that have implemented IDisposable, i suggest you to call
obj.Dispose and set it to obj = Nothing (or null) when you dont need him
any more.

All textboxes, panels, forms, comboboxes and other controls and datasets
etc, which are on the forms, which have IDisposable implemented?

Cor

[Josip Habjan]

no .. you misunderstand me.. or i explaned wrong....

see:
http://gotdotnet.com/team/libraries/...anagement.aspx

Regards,
Josip Habjan
URL: http://www.habjansoftware.com


"Cor Ligthert" <no************ @planet.nl> wrote in message
news:e%******** ********@TK2MSF TNGP14.phx.gbl. ..

Josip,

For all objects that have implemented IDisposable, i suggest you to call
obj.Dispose and set it to obj = Nothing (or null) when you dont need him
any more.

All textboxes, panels, forms, comboboxes and other controls and datasets
etc, which are on the forms, which have IDisposable implemented?

Cor

[Josip Habjan]

And also:
#1: http://weblogs.asp.net/pwilson/archi.../20/77435.aspx
#2:
http://msdn.microsoft.com/library/de...sposeTopic.asp
#3: http://www.codeproject.com/dotnet/GC_101.asp
.... etc...

Regards,
Josip Habjan
URL: http://www.habjansoftware.com

"Cor Ligthert" <no************ @planet.nl> wrote in message
news:e%******** ********@TK2MSF TNGP14.phx.gbl. ..

Josip,

For all objects that have implemented IDisposable, i suggest you to call
obj.Dispose and set it to obj = Nothing (or null) when you dont need him
any more.

All textboxes, panels, forms, comboboxes and other controls and datasets
etc, which are on the forms, which have IDisposable implemented?

Cor

[Cor Ligthert]

Josip,

In your first by you supported link I did not see what you wrote, as well
not on the other from Microsoft. Adviced is that when you use unmanaged
resources to implement Idisposable.

This is already implemented in any class that inherits from component. Which
is 80% of the in my opinion in general most used. And as Jon Skeet ones has
checked 20 % of the actual ones. Disposing is mostly done in the higher
class itself. See for that the part in the hidden part of a form or a
component. This you find back in almost all samples from Microsoft about
dispose.

On the blog page there is an explanation that is for me the same as: "What
does it harm to set all integers that you have created in your procedure to
zero". If you don't understand what I want to say with that. Just leave it,
however this tells for me only something about the knowledge from the
writers of this kind of sentences.

I hope this helps,

Cor

[Josip Habjan]

Cor,

From my point of view, MS should keep C++ concept on creating and destroying
objects. If you create new object instance, then you are responsible to
destroy it. In framework, GC may implicate on preformances since he decides
when he will call suppressfinaliz e. ( I know that he is waiting for best
time, but anyway )....

I have habit to call object.dispose (and =nothing) for every object instance
that i create (except: Usercontrols, string, integer and related types).
This way, i'm shure that my application will close immediate when i close
it, and will not stay in memory for next 5 minutes (waiting for GC to do his
work) ...

Regards,
Josip Habjan
URL: http://www.habjansoftware.com

"Cor Ligthert" <no************ @planet.nl> wrote in message
news:Oh******** ******@TK2MSFTN GP14.phx.gbl...

Josip,

In your first by you supported link I did not see what you wrote, as well
not on the other from Microsoft. Adviced is that when you use unmanaged
resources to implement Idisposable.

This is already implemented in any class that inherits from component.
Which is 80% of the in my opinion in general most used. And as Jon Skeet
ones has checked 20 % of the actual ones. Disposing is mostly done in the
higher class itself. See for that the part in the hidden part of a form or
a component. This you find back in almost all samples from Microsoft about
dispose.

On the blog page there is an explanation that is for me the same as: "What
does it harm to set all integers that you have created in your procedure
to zero". If you don't understand what I want to say with that. Just leave
it, however this tells for me only something about the knowledge from the
writers of this kind of sentences.

I hope this helps,

Cor

[Cor Ligthert]

Josip,

I think that we both have a different idea. I keep it by managed code.

However, that from the GC in your application is strange. My experience is
that the GC starts direct as soon as there is a kind of idle time in the
application. Even when the Graphical processor takes over the painting on
screen.

Cor

[Jon Skeet [C# MVP]]

Josip Habjan <jh*****@SPAM-OFF.net.hr> wrote:

I have habit to call object.dispose (and =nothing) for every object instance
that i create (except: Usercontrols, string, integer and related types).
You can't call Dispose on most types though - there are plenty of types
which don't implement IDisposable.

Also note that setting a variable to nothing is rarely useful, IME.
This way, i'm shure that my application will close immediate when i close
it, and will not stay in memory for next 5 minutes (waiting for GC to do his
work) ...

Disposing of an object doesn't garbage collect it.

--
Jon Skeet - <sk***@pobox.co m>
http://www.pobox.com/~skeet
If replying to the group, please do not mail me too