Menu
▾
▴
[Oorexx-bugs] [ oorexx-Bugs-1836829 ] OLEObject - memory leak in DISP_E_EXCEPTION handling
|
From: SourceForge.net <no...@so...> - 2007-11-23 05:29:06
|
Bugs item #1836829, was opened at 2007-11-22 20:53 Message generated for change (Comment added) made by miesfeld You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=684730&aid=1836829&group_id=119701 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Classes >Group: 3.3.0 >Status: Pending >Resolution: Fixed Priority: 5 Private: No Submitted By: Mark Miesfeld (miesfeld) Assigned to: Mark Miesfeld (miesfeld) Summary: OLEObject - memory leak in DISP_E_EXCEPTION handling Initial Comment: In OLE Automation when IDispatch::Invoke returns DISP_E_EXCEPTION the OLE object fills out an EXCEPINFO structure. Some fields in that structure are allocated BSTRs that it is the responsibility of the client (ooRexx in this case) to release. In the current code, the BSTRs are only released when the OLE object provides a deferred fill-in function. This is incorrect, they always need to be released. Whether the OLE object allocates them immediately or defers their allocation, the net effect is the same. They are allocated by the OLE object and need to be released by the client. ---------------------------------------------------------------------- >Comment By: Mark Miesfeld (miesfeld) Date: 2007-11-22 21:29 Message: Logged In: YES user_id=191588 Originator: YES Committed revision 1289. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=684730&aid=1836829&group_id=119701 |