Issue 54647

Summary: 100% CPU usage or crashing after moving horizontal lines in table
Product: Writer Reporter: sergio_nsk <sergio_nsk>
Component: formattingAssignee: michael.ruess
Status: CLOSED DUPLICATE QA Contact: issues@sw <issues>
Severity: Trivial    
Priority: P3 CC: issues, rainerbielefeld_ooo_qa
Version: OOO 2.0 Beta2Keywords: oooqa
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
URL: http://softage.ru/msv/Plan-2005-2010.odt
Issue Type: DEFECT Latest Confirmation in: ---
Developer Difficulty: ---
Attachments:
Description Flags
This file is needed to reproduce the issue 54647 none

Description sergio_nsk 2005-09-15 11:48:45 UTC 
OO: 1.9.125 localized and patched by Infra-Resource (Russia)
OS: Windows XP Professional, SP1

Can be easy reproduced.
Here is the file: http://softage.ru/msv/Plan-2005-2010.odt
The content is in the russian.

Please move several times the table border lines (especially horizontal) with
help of the mouse and the swriter will do one of the next items:
 - use CPU 100% for enough long time (more than 15 seconds) and then ok
 - use CPU 100% for a long time (more than 3 minutes), and the swriter should be
killed
 - crash.

Probably can't be reproduced on the original build or localized in another langauge.
Comment 1 sergio_nsk 2005-09-15 11:51:59 UTC 
Created attachment 29578 [details]
This file is needed to reproduce the issue 54647
Comment 2 Rainer Bielefeld 2005-09-16 07:50:33 UTC 
I checked with 2.0 (1.9.m125) German version WIN XP: [680m125(Build8947)] on PC
with AMD Athlon (3200+) and ATI READON 9600 graphics adaptor; I can confirm the
problem. I moved cell borders by mouse in 'Plan-2005-2010.odt' and from time to
time a get a app. 1 minute period with 100% CPU load.
Comment 3 Rainer Bielefeld 2005-09-16 07:55:09 UTC 
Related to issue 52781?
Comment 4 sergio_nsk 2005-09-16 08:52:23 UTC 
Probably you are right and the issue 54647 is related to the issue 52781.
Comment 5 michael.ruess 2005-10-05 10:26:50 UTC 
Yeah, it looks like issue 52781. Please check this here again with Build 680m132
or newer, where issue 52781 should be fixed in.

*** This issue has been marked as a duplicate of 52781 ***
Comment 6 michael.ruess 2005-10-05 10:27:55 UTC 
Closing duplicate.