Issue 29434 - X memory usage increases when opening particular document
Summary: X memory usage increases when opening particular document
Status: CLOSED FIXED
Alias: None
Product: Writer
Classification: Application
Component: code (show other issues)
Version: OOo 1.1.1
Hardware: PC Linux, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: ulf.stroehler
QA Contact: issues@sw
URL:
Keywords: crash, oooqa
Depends on:
Blocks:
 
Reported: 2004-05-24 10:28 UTC by richlv
Modified: 2013-08-07 14:41 UTC (History)
1 user (show)

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


Attachments
file with fontwork objects (6.14 KB, application/vnd.sun.xml.writer)
2004-05-24 10:29 UTC, richlv
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description richlv 2004-05-24 10:28:38 UTC
testcase contains two shapes – curve & freeform line. document was created in 
oo.org.
both shapes have text added and formatted with fontwork.
after text was added to the freeform shape and formatted to be red oo.org 
started to respond slower. closing and reopening of the document didn't help. 
after restarting oo.org this document now doesn't open – it hangs oo.org. during 
opening when/if oo.org has focus, memory usage of the process X goes up until 
available memory is exausted, then oo.org gets killed.

slackware-current, xfree86 4.4.0, S3 Inc. VT8375 [ProSavage8 KM266/KL266], 
xfree86 uses driver “savage”.
Comment 1 richlv 2004-05-24 10:29:33 UTC
Created attachment 15410 [details]
file with fontwork objects
Comment 2 Joost Andrae 2004-05-24 11:59:02 UTC
JA: cannot confirm this. Maybe this is a X issue
Comment 3 richlv 2004-05-24 12:29:44 UTC
checked this also on other machine. xfree86 4.4.0, i810 driver.
any ideas how i could debug this further ?
Comment 4 lohmaier 2004-05-24 18:43:41 UTC
can confirm with OOo 1.1.1 (german) running on linux with XFree86 4.3.0 (gnome
2.6, kernel 2.4.25)

OOo doesn't crash when OOo is already running. It only crashes when OOo is
invoked with the bugdoc as an argument.
So to reproduce close all instances of OOo and run
<path/to/>soffice slow.sxw
Since only a specific document is concerned and the crash can be circumvented ->
Prio lowered to 3
Comment 5 richlv 2004-05-25 06:22:25 UTC
i always open documents from oo.org (file->open). for me on both cases it 
crashes/leaks even if oo.org is open (doesn't matter if it has already some 
documents open or not).
Comment 6 rayll 2004-05-26 18:52:30 UTC
cannot confirm crash or memory leak on Suse 8.2, XFree86-4.3.0-120, OOo 1.1.1.

it does seem to render slowly when scrolling document UP using mouse wheel.
scrolling DOWN is very fast.  "top" shows that the soffice.bin executable
is sucking up the CPU while repainting the window after a scroll up.

this CPU spike occurs even if the text is not actually exposed and visible.
for example, if i send the OOo window to the background and cover it up with
a konsole, then hover over the OOo window and scroll the mouse, I see the
CPU spike when scrolling up, even though the red text is obscured by the
konsole window in the foreground.

hope it helps
Comment 7 richlv 2004-07-09 11:36:43 UTC
i'm unable to change version, but this is still true for version 1.1.2. memory 
usage increases until free memory is exausted or soffice.bin is killed (it 
responds to -15 and nicely closes)
Comment 8 michael.ruess 2004-07-22 17:05:39 UTC
To me, this sounds like a problem of the X server (as JA assumed above). When
trying to display "complex" graphical objects, it seems to have a memory leak.
What are the other's opinions about that?
Comment 9 michael.ruess 2004-08-02 10:40:37 UTC
Does the problem also occur, when these objects are are inserted into a
Drawing/Presentation document?
Comment 10 richlv 2004-08-02 12:47:07 UTC
i created a drawing document in windows, where i just copied both fontwork 
objects. this file works ok in windows (1.1.2), is slower in linux (scrolling, 
moving and resizing of the object) - but there is no increase in x memory usage.

this slowness when scrolling in draw is also observable when fontwork objects 
are out of visible area. cpu usage of soffice.bin increases up to 90%.

it's the same for impress - everything get's slow, but no memory usage increase.

i probably will see as this issue resolves and depending on that fill or don't 
fill another one for draw/impress and test calc :)
Comment 11 lohmaier 2004-08-03 21:24:23 UTC
I doubt it depends on the X-Server. At least this does not explain my
(reproducible) observations:
* No crash when OOo is already running (document loads pretty fast)
* When starting OOo with the document as argument OOo gets killed because of
extensive memory consumption (It does not crash itself, it gets killed by the
kernel)

I tried this again with OOo 1.1.2 and got the same results as with OOo 1.1.1
OOo1.9m47 doesn't have this problem.

I don't belive that a leak in X's memory handling depends on how OOo is invoked
(but maybe this makes a difference).

Can you confirm that much more memory is needed when OOo is started with the
document (OOo is not running before trying to open the document)?
Comment 12 michael.ruess 2004-09-06 14:58:20 UTC
The one we talked about in the meeting; please care about it.
Comment 13 ulf.stroehler 2004-09-06 16:06:56 UTC
Runs perfect with 680_m51. Considering as fixed.
Comment 14 ulf.stroehler 2004-09-06 16:07:42 UTC
Closing fixed issue.
Comment 15 cuodenumyp 2010-11-10 23:09:09 UTC
Created attachment 73816