To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=73457
------- Additional comments from [EMAIL PROTECTED] Fri Feb 2 13:35:13 +0000 2007 ------- Almost there. This one has taken more effort to get to the bottom of than I though. Sorry. One of the consequences of this diagnosis is that I've realised that the leak is a consequence of the assumption embedded in the code that all method calls return a value. Hence the leak occurs for ANY method call which doesn't. So if you replace the above For loop to a call to c.setValue(1) where c is ThisComponent.Sheets.Sheet1.getCellByPosition(0,0) for example. This extends the scope and impact of the leak to any basic code which is doing a lot of .setXXXX calls. Hence my recommendation to raise this to a P2. However, I hope to have the code fix finalised this weekend. //Terry --------------------------------------------------------------------- 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]
