Hi, 
 
I'm running a .Net application that makes use of XML (including XSL
Transformations) and database access (SQL Server).
One of the batches I'm running keeps failing due to "OutOfMemoryException".
I've monitored it and saw that the problem occurs when performing a
transformation, loading XML Documents and when dealing with large
strings (~1.5M) - I gain between 3 to 30 M for each task in that batch
(in a loop).
I'm not concatenating strings, and using "string builder" whenever possible. 
I've tried calling "GC collect" and "wait for pending finalizers", but
it doesn't solve the problem.
I'm considering moving some of the processing to a different
AppDomain, and killing it after each use, but I don't like this
solution (which will probably cause new issues anyway).
I'm disposing of everything that is disposable (or that can be
"closed"), and now I'm caching files, and database tables into memory.
I don't use unmanaged code, and I'm looking for a way to decrease the
footprint of each task to less than 1M, or alternatively to gain
better control of the GC.
Thanks,
Massiep.

are you using VB.Net?
There were stack size limitations in earlier versions of VB (Vb6)

No. I'm using C#.

it would help a bit my disposing off the connection or any other
reader object instead of just closing it. You can call the
connection.Dispose method to close the connection.

Could you post the c# code from your loop?  It would help us to
troubleshoot the issue.  Thx.