Issue 48765 - ooo 1.95 crash or irresponsiveness
Summary: ooo 1.95 crash or irresponsiveness
Status: CLOSED FIXED
Alias: None
Product: Writer
Classification: Application
Component: editing (show other issues)
Version: OOo 2.0 Beta
Hardware: PC Windows XP
: P2 Trivial (vote)
Target Milestone: ---
Assignee: michael.ruess
QA Contact: issues@sw
URL:
Keywords: needmoreinfo, oooqa
Depends on:
Blocks:
 
Reported: 2005-05-05 11:41 UTC by reuss
Modified: 2013-08-07 14:42 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 reuss 2005-05-05 11:41:10 UTC 
i tried to load the oasis opendoc specification v.3 .sxw in ooo1.14 and ooo1.95
and both became irresponsiveness with 100% processor load, 100 mb ram occupied.
both ooo was unusable: the most simpler click took at least 2 to 3 minutes. it
was a 670 pages document. the rest of the system and the other applications
continued to work fine and this problem affected ooo. i have a 800 mhz system
with 256 megs of ram.
Comment 1 michael.ruess 2005-05-09 11:29:09 UTC 
Reassigned to ES.
Comment 2 eric.savary 2005-05-12 16:37:38 UTC 
Please add a link to the specification
Comment 4 reuss 2005-05-12 20:49:52 UTC 
at first sight, it seems ok, but you should now load the navigator panel and
jump to a header title. It seems ok too, but then, jump to an other or a third
header title -> ooo is blocked
Comment 5 thackert 2005-05-15 13:55:35 UTC 
@reuss: The same happens here if I use the navigator with OOo-m100 under NLD 9 with an 
Athlon XP 2200+ and 1 GB of RAM... :( If I just use the <Page Up>, <Page down> or the up or 
down arrow, there is no problem at all ... :( And also my mouse wheel functions as it should ...
Comment 6 eric.savary 2005-05-17 15:24:46 UTC 
ES->OD: as described.
Comment 7 Oliver-Rainer Wittmann 2005-05-18 12:58:39 UTC 
no crash, update of navigator takes too long.

OD->HBRINKM:
Please take over as discussed.
Investigations reveals that the navigator updates via timer event its content.
If the outline content is visible, this update takes longer than the timeout of
this timer. Thus, nothing else then updating the navigator is performed.
Looking at method <SwContentType::FillMemberList(..)>, which performs the
intrinsic update, reveals that method <SwNodes::UpdateOutlineNodeList()> is
called 3 x <Count of outline nodes> + 1 during the update of the outline list.
In the given document the count of outline nodes is > 1800. I assume that this
cause the performance problems.
Comment 8 openoffice 2005-05-23 09:05:11 UTC 
.
Comment 9 openoffice 2005-08-10 10:58:42 UTC 
fixed in swnumtree
Comment 10 openoffice 2005-09-29 09:45:25 UTC 
ready for QA

re-open issue and reassign to mru@openoffice.org
Comment 11 openoffice 2005-09-29 09:45:34 UTC 
reassign to mru@openoffice.org
Comment 12 openoffice 2005-09-29 09:45:50 UTC 
reset resolution to FIXED
Comment 13 michael.ruess 2005-10-12 19:22:51 UTC 
Verified fix in CWS swnumtree.
Comment 14 michael.ruess 2005-11-11 07:59:36 UTC 
Checked fix in build 680m139.