To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=57599
                  Issue #:|57599
                  Summary:|Images With Transparent PNG Files Consume Xserver
                          |Memory On Remote Display
                Component:|Word processor
                  Version:|OOo 2.0
                 Platform:|All
                      URL:|
               OS/Version:|All
                   Status:|NEW
        Status whiteboard:|
                 Keywords:|
               Resolution:|
               Issue type:|DEFECT
                 Priority:|P3
             Subcomponent:|printing
              Assigned to:|mru
              Reported by:|drichard





------- Additional comments from [EMAIL PROTECTED] Wed Nov  9 13:32:58 -0800 
2005 -------
This is a very odd bug, but I have verified that this is happening.

On documents with embedded PNG images when you attempt to print it, it uses up
all of the local Xserver memory until there is none left and OOo then terminates
and closes.  I don't understand why it's using memory of the thin client, and
not from the binary running on the server, but for some reason it is. :|   The
amount of memory it uses is just amazing.  We have 40MB on our thin clients and
you can log into GNOME and crank up the OOo UI and still have 35MB left over. 
These print jobs are consuming it all and still not finishing.

It only happens when they are in PNG format.  I extracted the .odt file that was
hanging and then converted them all to JPG format and it worked fine and the
print process barely showed up on the memory monitor utility.

I'm attaching the following files as proof of this issue:
ooo_memory.png  - The shot of memory usage with OOo and document open.
ooo_memory2.png - The shot of memory usage and OOo terminated.  You can see
        in the memory graph that the thin client completely ran out of memory.
JUVDecembercalwpic.odt - The document that was used.
JUVDecembercalwpic_jpgformat.odt - The PNG files removed, converted to PNG.

This is virtually a showstopper for us for many documents.  The user community
will not understand how to extract those images and convert them.  Something is
looping or leaking in the PNG printing code.  

One should be able to simulate this I would think about watching the memory
usage of the "X" process on a Linux workstation.  It's cacheing something.

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