Trace the cause of this exception?

Quote:

---

An unhandled exception of type 'System.OutOfMemoryException' occurred in system.drawing.dll

---

I keep getting this exception when I run my application.

I use the drawing namespace since my app is performing a lot of printing. Is there a way to trace the memory? I think Im very careful in my code, Those objects that has a dispose method I always call, and I set all my own objects to nothing when I have no more use for them...

What other means do I have of controlling memory allocation??
memory leaks is not an option here since this is an important component to be used by lots of other programmers, and if I do have them it is a crisis... :(

Help...

Im using lots of objects that are made by me (the classes that is)... perhaps I don't destruct them correctly?

I know about garbage collection... but then why do I keep getting this exception?

kind regards
Henrik

Post your code, we can help u better

Thanks

The problem is that there is a lot of code, 15 classes... and our company policy actually forbid it :(

What I was looking for was rather some general "hints" on how to handle objects, where to destroy them and how to perform final cleanup when the program that uses the dlls is ended...


And since the exception occured in drawing.dll, perhaps this has nothing to do with my classes at all?


kind regards
henrik

ps Im sorry about the code, I really wish I could post it ds