How can I reduce memory in VB.NET Windows application?

Question

I am working on VB.NET multiuser application and whenever any of my forms opens up - memory rises, and after some time OutOfMemoryException is thrown.

I am working on VB.net 2008 and SqlServer 2005. I have used very many of shared object so second time its memory allocation is less, but how i can reduce it when form is closed or not in use. Can i use Garbage collector or Dispose and how I use this functionality ?

Brian Rasmussen · Accepted Answer · 2010-09-25 07:37:55Z

3

Are you detaching all event handlers as needed? This is a common source of memory leaks in .NET applications.

You can troubleshoot this by using tools like ANTS Memory Profiler or if you prefer a free option WinDbg+SOS is very useful (but not as easy to use).

edited Sep 25, 2010 at 7:37

answered Sep 24, 2010 at 7:50

Brian Rasmussen

117k34 gold badges227 silver badges325 bronze badges

Sign up to request clarification or add additional context in comments.

8 Comments

Brian Rasmussen Over a year ago

That could be the problem then. It is not a problem if both subscriber and publisher have the same lifespan, but if the publisher stays all subscribers will stay as well unless you detach the handlers.

KuldipMCA Over a year ago

but i am not using add handlers in my project so i dont need to use remove handlers.

KuldipMCA Over a year ago

any thing else you are talking about ?

KuldipMCA Over a year ago

please give me any example of this.

Brian Rasmussen Over a year ago

@KuldipMCA: It is hard to tell from your question how your application is designed, but if you have a GUI its unlikely that you don't have any event handlers.

|

jimplode · Accepted Answer · 2010-09-24 07:50:32Z

2

using .net Garbage collection is an automatic process, getting rid of any unused objects in memory.

A lot of memory can be "lost" to the program while waiting for garbage collection.

Normally you should leave the Garbage Collector alone. It usually does a decent job of deciding when cleaning house will be worthwhile.

But you may wish to force its hand every now and then.

There is a very simple call to clear the garbage collection.

GC.Collect()

Hope this helps.

Although, you probably have some other issues to be getting out of memory exception.

Are you dealing with imagery by chance?

answered Sep 24, 2010 at 7:50

jimplode

3,5104 gold badges28 silver badges44 bronze badges

3 Comments

Brian Rasmussen Over a year ago

It is rarely advisable to call GC.Collect.

jimplode Over a year ago

Agreed. But sometimes it can be useful, like I stated it is prob some other issue.

jimplode Over a year ago

As stated you prob have another problem, as the garbage collection is usually pretty good at cleaning up. I would try doing what Brian Rasmussen has suggested.

Mousa Alfhaily · Accepted Answer · 2017-08-28 07:00:29Z

2

Try this code for RAM MEMORY released :

First declare this function :

Private Declare Function SetProcessWorkingSetSize Lib "kernel32.dll" (ByVal hProcess As IntPtr, ByVal dwMinimumWorkingSetSize As Int32, ByVal dwMaximumWorkingSetSize As Int32) As Int32

And this is the usage of it :

Friend Sub ReleaseMemory()
    Try
        GC.Collect()
        GC.WaitForPendingFinalizers()
        If Environment.OSVersion.Platform = PlatformID.Win32NT Then
            SetProcessWorkingSetSize(System.Diagnostics.Process.GetCurrentProcess().Handle, -1, -1)
        End If
    Catch ex As Exception
        LogError(ex.ToString())
    End Try
End Sub

edited Aug 28, 2017 at 7:00

Mousa Alfhaily

1,3004 gold badges22 silver badges40 bronze badges

answered Jul 1, 2013 at 6:55

venkat

212 bronze badges

Comments

the_lotus · Accepted Answer · 2010-09-24 15:37:56Z

0

Make sure you remove all reference to an object when you don't need it anymore. (or all reference to the parent object)

If one of your active forms still uses an object you don't need, the garbage collector will assume you still need it and won't remove it from memory.

Don't forget to call .Dispose() when needed.

There's some great tool out there that can give you a hint on where your memory problem is.

answered Sep 24, 2010 at 15:37

the_lotus

12.8k3 gold badges39 silver badges55 bronze badges

Comments

EnFXCHILE · Accepted Answer · 2014-10-24 13:38:26Z

-6

The best :

Public Class FreeMemory Private Declare Function SetProcessWorkingSetSize Lib "kernel32.dll" ( _ ByVal process As IntPtr, _ ByVal minimumWorkingSetSize As Integer, _ ByVal maximumWorkingSetSize As Integer) As Integer

Public Shared Sub FlushMemory()
    GC.Collect()
    GC.WaitForPendingFinalizers()
    If (Environment.OSVersion.Platform = PlatformID.Win32NT) Then
        SetProcessWorkingSetSize(Process.GetCurrentProcess().Handle, -1, -1)
    End If
End Sub

End Class

answered Oct 24, 2014 at 13:38

EnFXCHILE

1

1 Comment

crashmstr Over a year ago

So you posted an almost duplicate answer (only difference is you removed a catch) but with only slightly better code formatting?

Collectives™ on Stack Overflow

How can I reduce memory in VB.NET Windows application?

5 Answers 5

8 Comments

3 Comments

Comments

Comments

1 Comment

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

5 Answers 5

8 Comments

3 Comments

Comments

Comments

1 Comment

Your Answer

Sign up or log in

Post as a guest

Related