Problem: too many GDI objects in memory

[Guest]

Hi all.
I have a very frustrating problem with my VB applications (developed with
VS2002/.Net1.0):
every application (even "stupid" two-forms application :-( ) seems to
allocate GDI resources
when a form is "opened" and doesn't release them after closing.
This "problem" (or bug? or coding error?) causes my application to become
very "slow" and a BIG number of allocated GDI objects.

Can you help me? Any idea about to solve this behaviour of .NET1.0?
Maybe the problem is VS2002 and .NET1.0: I read on the net of a lot of
memory-leak problems using GDI technology with .Net1.0. I'll solve my
problem upgrading to VS2003?
Thanks in advance for your answers.

 

[Armin Zingler]

Can you help me? Any idea about to solve this behaviour of
.NET1.0? Maybe the problem is VS2002 and .NET1.0: I read on the net
of a lot of memory-leak problems using GDI technology with .Net1.0.
I'll solve my problem upgrading to VS2003?

The question is not related to the VB.NET language. Please turn to the
appropriate microsoft.public.dotnet.framework.* group.

 

[Herfried K. Wagner [MVP]]

I have a very frustrating problem with my VB applications (developed with
VS2002/.Net1.0):
every application (even "stupid" two-forms application :-( ) seems to
allocate GDI resources
when a form is "opened" and doesn't release them after closing.
This "problem" (or bug? or coding error?) causes my application to become
very "slow" and a BIG number of allocated GDI objects.

Are you referring to that?

<http://www.jelovic.com/dotnetbugs/index.html>
-> "#16"