Issue 94528 - Memory Leak in soffice.bin
Summary: Memory Leak in soffice.bin
Status: CLOSED FIXED
Alias: None
Product: General
Classification: Code
Component: code (show other issues)
Version: OOo 3.0
Hardware: PC Windows XP
: P3 Trivial with 2 votes (vote)
Target Milestone: ---
Assignee: thorsten.martens
QA Contact: issues@framework
URL:
Keywords: needmoreinfo
Depends on:
Blocks:
 
Reported: 2008-10-01 12:04 UTC by vreid47362
Modified: 2010-07-01 12:36 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description vreid47362 2008-10-01 12:04:29 UTC
I have noticed the following behavior with OpenOffice 3 RC3 that may indicate a
memory leak.

On logon, the OpenOffice Quickstarter program starts.  It appears to start 2
processes, soffice.bin and soffice.exe.  On my system at logon to my user
profile, soffice.bin uses 18,272K of memory and soffice.exe uses 9,060K of memory.

After I start OpenOffice Writer and then close it, soffice.bin does not release
all of its used memory.  It continues to use 43,232K.

Next, if I open OpenOffice Calc and then close it, soffice.bin continues to use
even more memory:  53,312K.

Next, if I open OpenOffice Draw and then close it, soffice.bin continues to use
even more memory:  62,536K.

This pattern of additional memory usage continues each time I open up an
OpenOffice application and then close it.  Even after the machine sits idle,
with only the quickstarter program running in the task bar, the memory
allocation of soffice.bin continues and the additional memory stays allocated to
the process.

I am able to consistently reproduce this behavior.  I made my observations using
the processes tab of the Windows Task Manager.
Comment 1 vreid47362 2008-10-15 12:04:38 UTC
I am noticing the same memory consumption problem in OpenOffice 3.0 Release to
Production version.
Comment 2 asheman 2008-11-17 22:58:40 UTC
today I opened a word document.  and did nothing with it.  a few hours later my 
laptop started running slow.  I checked the processes and office.bin was user 
1.1gb of RAM.  This isn't the first time I have found office.bin to be using 
several hundred MB but is the first time it was over 1gb.  Seems obvious there 
is a problem with one of the extensions or the application. 

My extensions: French, English & Spanish spelling and thesaurus and the PDF 
Import extension.

FYI:  No wonder C# is what everyone is migrating to.  Memory leaks seem to be a 
problem with 9 out of 10 Java based programs I've encountered.  I've even seen 
them in enterprise applications written by well known companies like IBM.  I am 
sure the root cause is poorly written code however, it is so bad that memory 
management needs to be included into the Java environment or Java will go the 
way of Cobol.
Comment 3 ealaniz 2009-01-13 15:00:27 UTC
i have problems as well, when openoffice is running I can see from the task
manager it is requiring alot of processing/memory. once i close the application
the soffice.bin continues to take 20-50% processing/memory. if i stop the
soffice.bin process then i have problems with firefox. so i need to restart my cpu.

is openoffice replying to these comments at all or are we left alone with this?
Comment 4 vreid47362 2009-01-31 18:50:48 UTC
Disabling Java, even completely uninstalling a JRE, seems to have no impact on
the memory leak.  It still appears, which seems to indicate a problem with a
core component.
Comment 5 rganswindt 2009-02-15 14:31:21 UTC
This problem seems to be associated with the Quickstarter toolbar app. The
unusual processor and memory demands cease when I exit it, and I do not have any
processor or memory issues when I leave it disabled, that is, I do not load it
during system start-up. The toolbar Quickstarter is nice, but I can survive
without it for a while.
Environment: (if this helps...)
OOo 3.0.1 installed on Windows Vista (the premium home flavor w/ latest updates)
running on an AMD Athlon X2
Comment 6 Olaf Felka 2009-08-06 07:03:32 UTC
Please try the upcoming OOo 3.1.1 . The related developer snapshot is
OOO310_m17. We've had some fixes in the Quickstarter area.
Comment 7 Olaf Felka 2010-07-01 12:36:51 UTC
No further answers indicate that the issue is fixed.