To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=112766
                 Issue #|112766
                 Summary|Massive 64bit Memory Leak
               Component|Word processor
                 Version|OOo 3.2.1
                Platform|All
                     URL|
              OS/Version|Linux
                  Status|NEW
       Status whiteboard|
                Keywords|
              Resolution|
              Issue type|DEFECT
                Priority|P2
            Subcomponent|code
             Assigned to|writerneedsconfirm
             Reported by|drichard





------- Additional comments from drich...@openoffice.org Mon Jun 28 16:55:27 
+0000 2010 -------
erAck mentioned on the IRC to create this report and mark it P2.  We deployed
3.2.1 on a 64bit Linux server for the first time and it's leaking horribly in
Writer.  Each time that users open new documents it's grabbing around 100M of
memory which is never released even after the document is closed and they return
to the Start Center.  Those that are opening and closing documents all day are
using 1, 2 or 3G of memory.  It's very easily to replicate.  I log in as a user,
and then just close and re-open documents the memory consumption goes up.

We never saw this issue on the 32bit version.

I'm attaching a screenshot of top showing how the users are using up far more
memory than they should.  

I tried to use valgrind, but was never able to get it past the first document
opened.  It continues to loop and report that Java was not found which is
blocking me from continued leaking.  I disabled Java and tried that and it's in
a loop requesting that I enable Java.   So the attached valgrind shows the first
document being opened, at which time I had to control-c out because of the java
dialog loop.  

Issues worth mentioning:
- Software is being run to remote display to thin clients.
- THin clients are set to 16bit color depth.

The work around was to purchase and install enough memory to hold our highest
concurrent loads, but this obviously is not a good long term solution.

---------------------------------------------------------------------
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: issues-unsubscr...@sw.openoffice.org
For additional commands, e-mail: issues-h...@sw.openoffice.org


---------------------------------------------------------------------
To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org
For additional commands, e-mail: allbugs-h...@openoffice.org

Reply via email to