System.Object[] holding on to Custom Lists?

[ngodugu]

Hi All,

I have multiple Custom Collection objects that inherit from CollectionBase.

When I profile the app using memory leak profiler, it shows that arrays of these objects are still in memory. The retention graph for all these objects is the same.



It shows that a System.Object[] is holding on to CustomCollection

My custom collection object is called OrderBuyerSellerList.
Any ideas?

Thanks in advance.
Neelima

[Brian Donahue]

Hello,

From this part of the picture, you wouldn't be able to work out why some objects are still on the managed heap. You can use some of the filters to try to work out the reason, for instance if the object needs to be disposed or has a finalizer pending. I'd have a look at the filters and see if they point you in the right direction.
_________________
Brian Donahue
Technical Support
Red Gate Software Ltd.
44 (0)870 160 0037 ext 8521
US and CAN 1-866-RED GATE ext 8521

[ngodugu]

Brian,

Thanks for responding. Would it help if I send the profiler results?

Thanks
Neelima

[ngodugu]

Is there a way to send you an attachment? Please let me know.

[Brian Donahue]

You can just send it to support@red-gate.com. We don't make any guarantees because we do not provide consultancy services, but it wouldn't hurt to have a 5-10 minute look at it.
_________________
Brian Donahue
Technical Support
Red Gate Software Ltd.
44 (0)870 160 0037 ext 8521
US and CAN 1-866-RED GATE ext 8521

[ngodugu]

The compressed version is about 63MB and it does not allow me to send the attachment that size. Not sure if there is another way to send the document.
Question
when I checked "object that are not disposed" filter.. the class list became empty. Does that mean that these lists are not potential memory leaks?

Thanks
Neelima

[Brian Donahue]

When I look at the resullts you sent I do see System.Object[645] attached to the GC Root in the Instance Retention Graph, but the live count of OrderBuyerSeller is only 1, using 32 bytes, so even if this is leaking it's not a very big one. I think the array size shown in the retention graph is the allocation size. The docs are not clear about where this information comes from though.

"Objects that are not disposed" is listing objects that implement IDisposable and haven't had their Dispose() method called as far as I can tell.

I don't see much of an indication of a memory leak at all as the performance counters between snapshot 2 and 3 hold pretty steady at 256MB.
_________________
Brian Donahue
Technical Support
Red Gate Software Ltd.
44 (0)870 160 0037 ext 8521
US and CAN 1-866-RED GATE ext 8521