Memory Grows

  • Thread starter Thread starter Mauricio Carlos Pires
  • Start date Start date
M

Mauricio Carlos Pires

I created a simple project with VB .NET using .Net
FrameWork 1.1.
This project has only a form without any controls. When a
move the mouse over the form, the processes memory grows.
Someone kwow what's happening?
 
I created a simple project with VB .NET using .Net
FrameWork 1.1.
This project has only a form without any controls. When a
move the mouse over the form, the processes memory grows.
Someone kwow what's happening?
Click to expand...

Every time Windows sends a mouse-move message to your app, the Windows
Forms library creates a new MouseEventArgs object and passes it to your
Form (even if you don't have a MouseMove event handler). Probably some
other objects are created too. Those objects won't be freed until a
garbage collection occurs, so Task Manager will show that your app is
consuming more and more memory as all these objects are created.

Don't worry about it. Once the app has consumed a certain amount of
memory, the framework will do a garbage collection and your app's memory
will drop back down. You'll also get a garbage collection if another
app needs some of the memory that your app is hogging. So that large
memory allocation should actually be pretty harmless.
 
Back
Top