Created attachment 108345 [details] The document that triggers the bug. I got reported one DOCX document, which causes LO to loop infinitely. The document opens and its first page display. Looping starts after a few seconds if user does not perform any action or immediately if user attempts to scroll the document. Tested on Windows on different versions of LO and AOO.
bug confirmed under Win7x64 using LibO 4.3.2.2 and 4.4.0.0.alpha1+ Build ID: 6ba8b7f5eacac969e4781d63718083a05491b1bc TinderBox: Win-x86@42, Branch:master, Time: 2014-10-24_02:23:51
Confirmed with v4.3.3.1 under mint 17 x64. Set to All.
In the 43-all bibisect repository, I see from `git bisect bad`: e65850d4d23beb93ded3cab9e5945dd39c530738 is the first bad commit commit e65850d4d23beb93ded3cab9e5945dd39c530738 Author: Bjoern Michaelsen <bjoern.michaelsen@canonical.com> Date: Wed Dec 7 05:16:40 2011 +0100 source-hash-a44dda4b7d71f8d2b4e0cca79d732eab89588c3a commit a44dda4b7d71f8d2b4e0cca79d732eab89588c3a Author: Matúš Kukan <matus.kukan@gmail.com> AuthorDate: Fri Sep 2 03:21:23 2011 +0200 Commit: Matúš Kukan <matus.kukan@gmail.com> CommitDate: Fri Sep 2 11:49:25 2011 +0200 process more idl files at once - second part: makefiles :100644 100644 6fbf255c3a7ff698bd1077b31bb78fc656d66c43 ab0595641102029f7ba0a38bda6553bf144f6d62 M autogen.log :100644 100644 9e5b8e49ccf5e2259565c67680a3fa8568ed582c f1776e218e615ee16234fda621551b17913e87b7 M ccache.log :100644 100644 496231332d58ca1dfc93e962b4023e5eedf14262 e4bfdb45b33fb0ec0cafb2b41f0b35a389bf26bd M commitmsg :100644 100644 ff78528271a5a87f4943854ba914b03498394775 b76274ecc9f917a09f00a032b12352db356e377b M dev-install.log :100644 100644 9d8b57d00ca90aa6e3601d10017dc532ec1bed28 d8894603ec34f90e21ef518aac5c5b0fa425b34e M make.log :040000 040000 58bc0ef52488b6b81c2f58a7ae59d22e08f31d94 015bad708b8e165da96667dcf17f583220b4ae10 M opt and from `git bisect log`: # bad: [423a84c4f7068853974887d98442bc2a2d0cc91b] source-hash-c15927f20d4727c3b8de68497b6949e72f9e6e9e # good: [65fd30f5cb4cdd37995a33420ed8273c0a29bf00] source-hash-d6cde02dbce8c28c6af836e2dc1120f8a6ef9932 git bisect start 'latest' 'oldest' # bad: [e02439a3d6297a1f5334fa558ddec5ef4212c574] source-hash-6b8393474974d2af7a2cb3c47b3d5c081b550bdb git bisect bad e02439a3d6297a1f5334fa558ddec5ef4212c574 # bad: [8f4aeaad2f65d656328a451154142bb82efa4327] source-hash-1885266f274575327cdeee9852945a3e91f32f15 git bisect bad 8f4aeaad2f65d656328a451154142bb82efa4327 # bad: [369369915d3582924b3d01c9b01167268ed38f3b] source-hash-45295f3cdceb4c289553791071b5d7f4962d2ec4 git bisect bad 369369915d3582924b3d01c9b01167268ed38f3b # bad: [351622aec2dff3cc3bbbb020ad0097c4322d2a21] source-hash-2c4537471c932b65e6f72e41881b505c4bbad12c git bisect bad 351622aec2dff3cc3bbbb020ad0097c4322d2a21 # bad: [035c276ec5a8da669e6043a3db6b0701dd3c2ade] source-hash-dc8249af103741415a074d9bbf8b1211f24a7c3f git bisect bad 035c276ec5a8da669e6043a3db6b0701dd3c2ade # bad: [4225403645019b6af53db0bf9ba9bbd063e9aa93] source-hash-cf16ef6c250a2755155a02f24bad861b35a1f92b git bisect bad 4225403645019b6af53db0bf9ba9bbd063e9aa93 # good: [07e8171f32b03a1146ef80d086c2dd61f3def5aa] source-hash-886762160996dfa3fee07cf135e53dfe952ed298 git bisect good 07e8171f32b03a1146ef80d086c2dd61f3def5aa # bad: [a0486a18ac4ea6508f02804cf2624c46607674af] source-hash-a0a1c3f4fb730ed3614593c3d8ddb50c23204c29 git bisect bad a0486a18ac4ea6508f02804cf2624c46607674af # bad: [f89e78929fb81d824ac5ad2b3063a7f73ed47c9a] source-hash-a705aec5117fe9123236ebdeb0d6f271b83f8af4 git bisect bad f89e78929fb81d824ac5ad2b3063a7f73ed47c9a # bad: [e65850d4d23beb93ded3cab9e5945dd39c530738] source-hash-a44dda4b7d71f8d2b4e0cca79d732eab89588c3a git bisect bad e65850d4d23beb93ded3cab9e5945dd39c530738 # first bad commit: [e65850d4d23beb93ded3cab9e5945dd39c530738] source-hash-a44dda4b7d71f8d2b4e0cca79d732eab89588c3a
(Commented during a sweep of bugs which are bibisected but not source bisected) This is so far back into the dark ages of the build system, I can't even get it to build from source. Nothing obvious stands out from the list of commits in the bibisect range either. Unfortunately this one will probably have to be debugged the hard way
Removing 'regression' as nothing suggests this ever worked.
Re-checked this and I can reproduce it on 3.3.0, so I'm going to have to agree that this isn't a regression. Unfortunately comment 3 looks like a false positive. The issue also occurs on current 4.5 master, although it is a little harder to trigger. Scrolling in pages 140-150 seems to still hang reliably. Removing Keywords:regression and Whiteboard:bibisected
Created attachment 113012 [details] Linux 4.5 master backtrace (from breaking into the hang)
Created attachment 113013 [details] .odt version of original document After converting the original file to an .odt from the command line, the .odt version also shows the same issue, so this is not specific to .docx. Scrolling around the page 140-150 region still triggers the same hang.
For me not reproducible with LO 5.1.0.1, Win 8.1 Does this issue still persist for other users with the latest release of LO?
you are right. bug is gone. tested with LibO 5.0.3.1 under Win8.1 x64 RESOLVED WORKSFORME
Works for me too now.