Memory usage continues to rise until OOM exception occurs.

Hey eveyone,

 

I have a fairly complex application which makes use of an MS Access database. My application generates some 14million entries and inserts them after each generation, into the database. The app works perfectly without any bugs(that I am aware of) apart from
one problem. If I run the app and let it run the full 14million odd data entries, the app crashes some way  through and giives an Out of Memory exception. I then loaded up TaskManager and notice that the memory usage increases by about 8-15Kb per second. 

I have done some reading and have tried using Dispose() to get rid of any objects finished with, I have tried building in release mode and the problem remains. I’m not even really sure if it is a memory leak or something else.

If anyone has any advice I would really appreciate it. Also, if there are some threads on the forum that are relevant then please provide them; I have searched the forum but have not found anyone really explaining this well.

I am using VS2010 and my application is running in .net 4.0.

Any additional information needed, just let me know.

 

Thanks!

Rick, I am involved with programs that do directory listings. The list view take 4096 butes of vituual memory  whether I use it or not (I dont but I get ‘charged’ charged for it.I don’t know what your I/o device is but it follows the same general pattern mine does. I would advise you to get a copy of procmon from Sys Internals and look at it.Renee

Garbage collection is a multi-step process, which occurs  across two phases.  An object if first logically disposed, which makes  the object unavailable for further referencing by your code.  Later, the more time-consuming process occurs to remove

Can you pinpoint the operation where the OOM exception  is triggered?–