Bug 64768

Summary: layout loop on a particular docx file when loading a particular page
Product: LibreOffice Reporter: Jorendc <jorendc>
Component: WriterAssignee: Not Assigned <libreoffice-bugs>
Status: NEW --- QA Contact:
Severity: major    
Priority: high CC: arnaud.versini, mst.fdo, vmiklos
Version: 4.0.0.0.alpha1Keywords: bisected, regression
Hardware: All   
OS: All   
Whiteboard: bibisected filter:docx
i915 platform: i915 features:
Bug Depends on:    
Bug Blocks: 58944    
Attachments: backtrace
bibisect log

Description Jorendc 2013-05-19 19:19:30 UTC
How to reproduce:
* Download attachment 72382 [details]
* Open it using LibreOffice

While opening that file you'll see that the page number increase (bottom left). When it's on page 25, libreoffice freezes (CPU to 100%).

Not reproducible using LibreOffice 3.6.6.2. On that version it opens 28 pages without a freeze.

Kind regards,
Joren
Comment 1 Jorendc 2013-05-19 19:20:13 UTC
On IRC:
<arnaud_versini> jorendc: I confirm, this is a bug :-)
Comment 2 Jorendc 2013-05-19 19:27:51 UTC
Created attachment 79543 [details]
backtrace
Comment 4 Michael Stahl 2013-05-28 17:01:20 UTC
was introduced by:

commit 355d25eac764713f4d52eac801ade6e2ff1deab0
Author: Cédric Bosdonnat <cedric.bosdonnat.ooo@free.fr>
Date:   Wed Sep 19 16:19:37 2012 +0200

    n#779627: added quite some compat options from the ww8 filter on writerfilter

specifically this setting:

    xSettings->setPropertyValue( "TableRowKeep", uno::makeAny( sal_True ) );


i guess we need that setting for MSO interop in general
even if it causes a loop on this particular file?
Comment 5 Björn Michaelsen 2013-06-27 10:19:22 UTC
Updating version as per Comment 4.
Comment 6 Cédric Bosdonnat 2014-01-20 08:57:14 UTC
Restricted my LibreOffice hacking area
Comment 7 Jorendc 2014-07-18 19:12:43 UTC
Still reproducible, tested using Mac OSX 10.9 with LibreOffice Version: 4.4.0.0.alpha0+
Build ID: eddd7646d672ea9b0561dacb09da224d098e531e
TinderBox: MacOSX-x86@49-TDF, Branch:master, Time: 2014-07-18_06:13:47
Comment 8 Björn Michaelsen 2014-10-16 14:59:03 UTC
(This is an automated message.)

It seems that the commit that caused this regression was identified. (Or at least a commit is suspected as the offending one.)

Thus setting keyword "bisected".

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.