1
Vote

EzAPI memory issues and disposing objects

description

There doesn't appear to be a way to clean up EzAPI objects. For example, every time I construct an EzDataFlow object, I see that both memory usage and the number of handles increase but I have no way of cleaning this up.

Sometimes, when I create enough EzDataFlow objects, I run into the following error:
Cannot create a task from XML for task "", type ", {5918251B-2970-45A4-AB5F-01C3C588FE5A}" due to error 0x8007000E "Not enough storage is available to complete this operation.".

I believe that clean up may be the cause of this. Is there any way around this?

Any help would be greatly appreciated.

comments