Virtual Memory low problem...

  • Thread starter Thread starter rollasoc
  • Start date Start date
R

rollasoc

Hi,

Another Friday afternoon problem to fix.

Our application, seems to run fine for several hours, then pops up with a
low virtual memory message. This sometimes then crashes the system, since it
will then say one of the objects has not been instantiated.

I'm assuming we've been a bit lax with the disposing of objects. Is there a
difinitive list of things we should be disposing manually?

The application is graphic intensive and we have been disposing of variosu
graphic \ pens and brushes objects, but what about temporary bitmaps (i.e.
backbuffers) etc.

Any tips as to what else I might need to Dispose rather than let the GC have
a goa t a unspecified point?

rollasoc
 
anything that you are creating that has an IDispose interface should be
disposed of as soon as you no longer need it. Anything else you should just
ensure that any references to items that you no longer need gt set to null
so that the garbage collection can tell it is no longer needed.

Lynn
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Virtual Memory problem. 2
about resources and the using 7
Disposal of GDI Resources and GDI Limits, a puzzling question (for meat least) 3
Memory Leaks in C# 5
Large virtual memory, small working set 1
Does .NET Framework 1.0 have unmanaged resource leaks? 5
Odd GDI bug - Full and complete example enclosed! 5
virtual memory low 4

Back
Top