To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=48858
                  Issue #:|48858
                  Summary:|Memory Leak in soffice.bin, visible with Quickstarter
                Component:|api
                  Version:|OOo 2.0 Beta
                 Platform:|PC
                      URL:|
               OS/Version:|Windows XP
                   Status:|UNCONFIRMED
        Status whiteboard:|
                 Keywords:|
               Resolution:|
               Issue type:|DEFECT
                 Priority:|P3
             Subcomponent:|code
              Assigned to:|sw
              Reported by:|punisher





------- Additional comments from [EMAIL PROTECTED] Sat May  7 06:55:49 -0700 
2005 -------
There is a memory leak in OpenOffice soffice.bin process, which is visible when
using Quickstarter.  I am using build 680m100.  

On first boot, the process loaded by Quickstarter, soffice.bin, consumes 15 MB
of RAM.  This is reasonable (and should be no greater).  Quickstarter itself
consumes and remains steady at 1,292 KB of RAM.  The fun begins when one
actually uses OpenOffice applications.  Rather than dismissing the leak as a
Windows Task Manager problem, an argument I do not accept since I have
applications on my systems that actively free memory they consume while the
application is in use, try the following out for yourselves.

There are six OpenOffice applications installed with 680m100.  Cycle through
each application by launching it, creating or opening and working with an
associated file, and then closing the application.  Upon closing each
application, note Memory Usage for the soffice.bin process, as reported by
Windows Task Manager.  This memory never gets freed and will grow and grow. 
Mine exceeded 85 MB, with no applications running - only Quickstarter - by the
time I filed this report.  This soffice.bin memory usage will, as I have
confirmed, continue to grow with each launch, usage, and close of OpenOffice
applications.  It never gets freed! 

After reviewing the other bug reports on memory leaks in the various OpenOffice
applications (i.e. bug reports: 48405, 48642, 41675, and especially 40658), it
appears this is a systemic problem.  This bug exists in one or more core
OpenOffice components, and it would be very much appreciated if this could be
fixed.  As a measure, I believe that soffice.bin, which begins life at 15 MB
with Quickstarter, should jettison memory and return to its initial memory
consumption with each application close.  Caveat: I am not a programmer, and I
do realize things aren't always so black and white, but there is a problem here.

Thanks

---------------------------------------------------------------------
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