When should finalize()/dispose() be called

(0) Share

Report

Posted on by Community Member

Does anyone know if there are circumstances in which I could encounter a memory leak if not calling finalize() or dispose() on an object.

Normally, I assume that an object instance that is declared locally gets garbage collected when leaving the method - but I would like to know if anyone has experienced anything else. I often use COM objects and/or .NET objects, and I don't know if they should be treated in a different manner.

Would be good to know...

/Jonas

*This post is locked for comments

I have the same question (0)

All responses (1)

Answers (0)

Suggested answer

Community Member on at

Like (0)

Report

Re: When should finalize()/dispose() be called

Hi Jonas,

Good question. x++ does not use destructors so I would assume if you were calling a .NET AX object you wouldn't have to call finalize() or dispose()

This is only my thoughts however. If anything use exception handling where ever you are making an instance of an object in your code.

Have a good week.

Was this reply helpful? Yes No