For ll_index = 1 to 100
lole_data = iole_wcf_client.tcp_d_maint_client_store_data_ret(FALSE)
Next
As you can see very simple. It looks like each loop the memory jumps up almost as if a new OLEObject is being created each time, but I have tried setting it to null, crating and destroying it to no avail.
That's actually what it does, creates a new object on each loop. Were you destroying within the loop?
The C# code, also pared down, but loading 1579 rows from an xml file is:
Just curious, but was closing the streamreader part of what got pared down?
You might also look at this. It indicates that the XmlSerializer can be a source of memory leaks as well if not handled properly:
Memory usage is high when you create several XmlSerializer objects in ASP.NET