Issue 17228 - Leaks (a lot of) memory after minimize
Summary: Leaks (a lot of) memory after minimize
Status: CLOSED DUPLICATE of issue 16909
Alias: None
Product: Writer
Classification: Application
Component: ui (show other issues)
Version: OOo 1.1 RC
Hardware: PC All
: P2 Trivial (vote)
Target Milestone: ---
Assignee: h.ilter
QA Contact: issues@sw
URL:
Keywords: crash, oooqa
Depends on:
Blocks:
 
Reported: 2003-07-22 12:46 UTC by klas
Modified: 2003-09-08 16:56 UTC (History)
2 users (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description klas 2003-07-22 12:46:50 UTC 
After editing (in my case opening a master doc and then a sub.doc, inkluding
many links to graphics etc.) and then on minimize/iconify, OO starts to leak
memory (using 99% CPU). Independent of if doc is saved or not. SP4 installed. No
idea if this is in Writer only, or if in UI or base code.
Comment 1 klas 2003-07-22 14:37:02 UTC 
Additional findings:
* Not related to master docs.
* Only fails when "Online layout" is active.
* Depends on document content (or paragraph styles)!

I have now a two page document without graphics that hangs Writer.
Will be sent to the one who takes a look at this problem. /Klas
Comment 2 derekhtodd 2003-07-29 19:22:06 UTC 
I can confirm on OOo 1.1rc

SuSE linux 7.3 glibc 2.2.4 kernel 2.4.20 xfree 4.2.0 freetype 2.1.4

75% CPU, memory leak got to 750M before I got bored and killed it

Steps to reproduce on my system;

- open writer
- type just the following two characters

1-

where '-' is a nonbreaking hyphen ( entered using ctrl+shift+[-] )

- press the online layout icon (botton left)
- minimize writer or switch to alternative desktop
- kaboom
Comment 3 dankegel 2003-07-30 05:29:57 UTC 
Reproduced on Red Hat 8 in OOo1.1rc2 with Derek's excellent recipe.
Got stack traceback with gdb, searched Issuezilla for first
interesting symbol, found issue 16909 has identical stack.
Thanks, all!

*** This issue has been marked as a duplicate of 16909 ***
Comment 4 h.ilter 2003-08-05 11:51:37 UTC 
.