Issue 44132 - Large nested tables cause possible memory leak in Writer
Summary: Large nested tables cause possible memory leak in Writer
Status: CLOSED DUPLICATE of issue 44141
Alias: None
Product: Writer
Classification: Application
Component: code (show other issues)
Version: OOo 2.0 Beta
Hardware: PC Windows XP
: P3 Trivial (vote)
Target Milestone: ---
Assignee: michael.ruess
QA Contact: issues@sw
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-03-04 23:31 UTC by jstimers
Modified: 2005-04-28 08:04 UTC (History)
1 user (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 jstimers 2005-03-04 23:31:53 UTC 
1.  Open a new document and create a table that has 16 columns and 1,024 rows
(the maximum allowed rows with 16 columns).
2.  Select the first cell from the first row and insert a table into it.  This
table should be 60 columns by 72 rows.

Initially it appears that the table is inserted into the cell, but then Writer
stops responding.  It also begins to take memory from the system at a very fast
rate.  In total it consumes about 250MB in about 5-10 minutes.

James Stimers
Ramneek Singh
Comment 1 michael.ruess 2005-03-18 14:16:44 UTC 
This is the same as issue 44141; high memory consumption on large tables. 

*** This issue has been marked as a duplicate of 44141 ***
Comment 2 michael.ruess 2005-04-28 08:04:43 UTC 
Closing duplicate.