To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=73457


User terrye changed the following:

                What    |Old value                 |New value
================================================================================
                 Summary|Memory Leak in Basic Argum|Memory Leak in all Basic t
                        |ent Handling              |ype void Method calls
--------------------------------------------------------------------------------




------- Additional comments from [EMAIL PROTECTED] Sat Feb 10 12:44:14 +0000 
2007 -------
*** FIX ***

The minimum impact change which removes this leak is a one line change to
sbxmod.cxx:
@@ -2057,7 +2057,8 @@
                if( mpPar.Is() )
         {
                        // this, als Element 0 eintragen, aber den Parent nicht
umsetzen!
-               mphoPar->PutDirect( pThisCopy, 0 );
+               if (GetType() != SbxVOID) mpPar->PutDirect( pThisCopy, 0 );
                        SetParameters( NULL );
         }

This change should be put in ASAP in 2.3 or 2.4, as it will close a major memory
leak in all applications which make heavy use of Basic.

Note that this whole code area has a number of implementation weaknesses that
impact heavily on runtime performance.  I've drafted a paper on this and sent to
AB for comment. I will attach it as background once AB has had a chance to 
comment.

---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to