To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=94716 Issue #|94716 Summary|Under Windows it leaks some resource related to the De |sktop Heap Component|Word processor Version|OOo 2.1 Platform|All URL| OS/Version|All Status|UNCONFIRMED Status whiteboard| Keywords| Resolution| Issue type|DEFECT Priority|P3 Subcomponent|save-export Assigned to|mru Reported by|sherter
------- Additional comments from [EMAIL PROTECTED] Mon Oct 6 21:07:53 +0000 2008 ------- We have noticed a Windows specific memory/resource leak in OpenOffice 2.1. We have been trying to track down what the problem is for a while now and we believe we have narrowed it down to the Desktop Heap. Below is a table showing the Windows Desktop Heap setting and the number of documents we managed to convert to PDF through a Java program using the UNO API. The command line we use to start OpenOffice: soffice.exe -nocrashreport -norestore -nolockcheck -nologo -nodefault - userid=".\UserInfo" -accept=socket,host=0,port=8100;urp Windows Desktop Heap Memory Number of Documents Converted to PDF 512 26,000 1024 54,000 3072 170,000 4096 227,000 8192 514,000 I have run a utility to track desktop heap memory and the memory was not slowly disappearing so it is probably a handle or an atom or some other low level Windows heap item that is not getting cleaned up. Unfortunately I can’t find a way to figure out what resource is getting leaked. The Windows Desktop Heap memory was manipulated through the following registry keys based on the Microsoft Knowledge Base article http://support.microsoft.com/kb/840342. We altered the SessionViewSize under registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management to allow us to set the SharedSection values we were testing under the registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\SubSystems. We were altering the third value for SharedSection which is the non-interactive desktop for our JEE application running as a service. The testing was done with a Java program converting the same document over and over to PDF. Open Doc, Store As PDF, Close Document. The process we use is to convert one off documents on a server so it is always a new document so it is opened, converted, and closed. Every 1000 uses, we closed OpenOffice and restart since we have found that around 3000 uses it starts to take several minutes for each convert and eventually crashes. The document is RTF but we have also tried .DOC and .ODT and got the same results as far as the Desktop Heap Memory being the controlling variable as to how many documents we got through before it crashed. We tried a couple of different documents from a simple one page letter to a more complex two page insurance Explanation of Benefits form that contained tables. The interesting thing was that this did not make a difference in the number of documents we got out before it crashed. This also indicates it is not strictly memory related but probably handle related and there is some table that is dynamically sized to the heap value and when it fills up it can no longer create items of that type and OpenOffice.org then crashes and cannot be started again without a reboot. We have also tried by writing a macro that would read a text file to tell it what document to open and what name to give the converted document. It gave us the same results as far as the number of documents converted before crashing to the point that the desktop had to be destroyed and re-created. (log off, log on when run interactively, reboot when run as a service). --------------------------------------------------------------------- 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]
