Problem description: Steps to reproduce: 1. open file (see file attached).... 2. change zoom factor to 200%.... 3. cry ;-).... Current behavior: crash
Created attachment 109760 [details] File that crashes with LO 4.3.4 and not with 4.2.7
Comment on attachment 109760 [details] File that crashes with LO 4.3.4 and not with 4.2.7 http://1drv.ms/1F7q2oL
As this bug seems to have been created in status NEW, I am setting it UNCONFIRMED and normal priority. Note that only with Internet Explorer running on Windows was I able to download the document by following the link in comment 03. Iceweasel on Linux downloaded a zero-length file. Neither on Windows nor with a recent LibreOffice on Linux was I able to come close to a zoom factor of 200%. (*) On Windows Vista with Version: 4.4.0.0.alpha2+ Build ID: 4f18bd405831c31cd49190046f7bafd805a47d7d TinderBox: Win-x86@39, Branch:master, Time: 2014-11-20_09:39:04 Locale: en_CA some time after my first zoom-in (plus sign in the zoom control in the status bar) the zoom factor was 120%. Two more zoom-in leave the entire Writer window grayed out and the mouse cursor is chasing its tail around; TasK Manager shows modest CPU usage (1%, 3%, 4%). (*) With daily dbgutil bibisect version 2014-11-20, I named the file on the command line. LibreOffice pegged the CPU essentially continuously, and I cancelled the job after at least five minutes. The terminal shows many instances (overflowing the terminal buffer) of the message: warn:sw.resizeview:13569:1:sw/source/core/view/vdraw.cxx:237: Trying to move anchor from invalid page - fix layouting! For comparison, the 43all bibisect repository version oldest opens the file promtly and zooms to and beyond 200% without any evident problem. I am *not* calling this bug a regression because I have not succeeded in reproducing the reporter's problem.
Created attachment 109796 [details] File that crashes with LO 4.3.4 and not with 4.2.7
I confirm bug in 4.3.0.4, 4.3.3.2 and 4.5.0.0 alpha under Win8.1 no crash with 4.2.6.2 hence regression, needs bibisecting
I do not reproduce in 4.5 master on Linux, and I get the following bibisect results from 44 (on the basis of a search for where it ceases to crash - "bad" means fixed here): 5b2c61f6b34f03146c2d03da03a7b7f546ce56b8 is the first bad commit commit 5b2c61f6b34f03146c2d03da03a7b7f546ce56b8 Author: Bjoern Michaelsen <bjoern.michaelsen@canonical.com> Date: Sat Oct 18 00:19:03 2014 +0000 source-hash-abf842e4b125b9f863ea4c2af17ad6ac7d82b15e commit abf842e4b125b9f863ea4c2af17ad6ac7d82b15e Author: Caolán McNamara <caolanm@redhat.com> AuthorDate: Thu Jun 5 10:16:52 2014 +0100 Commit: Caolán McNamara <caolanm@redhat.com> CommitDate: Thu Jun 5 13:35:53 2014 +0100 coverity#705323 Missing break in switch, assuming its intentional Change-Id: Ibb8fe4e1d13a24f810fbdf4978606c35890a9cfd # bad: [4a3091e95fa263d3e2dd81e56e83996f0bb12287] source-hash-2b5b04e1e62914bf0902dfd7943cdc44499c47a6 # good: [812c4a492375ac47b3557fbb32f5637fc89d60d9] source-hash-dea4a3b9d7182700abeb4dc756a24a9e8dea8474 git bisect start 'latest' 'oldest' # good: [5d0dfb8e62ae61a240f8313c594d4560e7c8e048] source-hash-0c6cd530de13f80795881f61064f1bf1dcc4ea81 git bisect good 5d0dfb8e62ae61a240f8313c594d4560e7c8e048 # bad: [7dfacd0b8bd828331d74c0f79de6e8924bc4e6a5] source-hash-f93ce4f7eb90093d0ea3115d0a1c614612676dbd git bisect bad 7dfacd0b8bd828331d74c0f79de6e8924bc4e6a5 # bad: [1a63057f6378db7c6b8af1171b7b140f7583f246] source-hash-59f84b4a2c082382767f12e0c7a06a3f0b52e721 git bisect bad 1a63057f6378db7c6b8af1171b7b140f7583f246 # bad: [3787e4f82e47eaf4fa454afdca671272e50f875b] source-hash-0e09134a4a4cbb0639fc586c560c6fb2765487be git bisect bad 3787e4f82e47eaf4fa454afdca671272e50f875b # bad: [5b2c61f6b34f03146c2d03da03a7b7f546ce56b8] source-hash-abf842e4b125b9f863ea4c2af17ad6ac7d82b15e git bisect bad 5b2c61f6b34f03146c2d03da03a7b7f546ce56b8 # good: [1022c199a7d20dde7600f08007b5e2cac81e55f4] source-hash-df903c3e2084d8cc33e3935a1668b8b46e25201f git bisect good 1022c199a7d20dde7600f08007b5e2cac81e55f4 # skip: [5ab97df01d7167dc7b472cf0f5b21fea4fccd232] source-hash-b651ed7a6700b560052b67102a65f06a498dd182 git bisect skip 5ab97df01d7167dc7b472cf0f5b21fea4fccd232 # good: [7e3ee4ad7f79565293c1ff9c20e099101435d3c1] source-hash-312ffe07bbef6b8dbc14ce38c0a726f69dd90946 git bisect good 7e3ee4ad7f79565293c1ff9c20e099101435d3c1 # good: [a40d8c51092e2ab68f3c483b782e5eac0fdf5e3b] source-hash-f18a86759b20d13c660a6224fe26451cb64bd92d git bisect good a40d8c51092e2ab68f3c483b782e5eac0fdf5e3b # first bad commit: [5b2c61f6b34f03146c2d03da03a7b7f546ce56b8] source-hash-abf842e4b125b9f863ea4c2af17ad6ac7d82b15e
Two obvious crashes are fixed in the above range, but the fixes had already landed in 4.3.3.2 which is mentioned as having been reproduced upon (I assume the version "4.3.4" mentioned in comment 1 refers to 4.3.0.4 as this is what the Version field is set to) Could the original submitter and/or reproducer please: - Confirm whether they still experience the crash in 4.3.5.1 / 4.4beta1 (or later) and/or current master - If it still crashes, follow https://wiki.documentfoundation.org/How_to_get_a_backtrace_with_WinDbg to get a Windows backtrace and attach it here If this is a genuinely Windows specific bug rather than what I bibisected above, then the backtrace will be needed to investigate any further. Setting to NEEDINFO - please set the status back to NEW when further information is attached (either the fact that it can no longer be reproduced on Windows, or a backtrace)
Created attachment 110826 [details] BackTrace I confirm crash with both 4.3.5.1 and 4.4.0
Created attachment 110829 [details] Bibisected backtrace to ignore - not the reported crash Thanks for following up. To avoid later confusion, the attached is a backtrace from the previously bibisected crash which has already been fixed. The two seem unrelated. I'm going to assume then that the but reported here isn't reproducible on Linux (at least not on 64-bit), so it's unfortunately not bibisectable -> Setting status back to NEW -> Changing to Whiteboard: notBibisectable There is also a partial backtrace attached to bug 83199 which resembles the backtrace supplied here, but I'm suspicious that several different crashes are getting mixed up in the reproduction here, so probably best not to merge the two bugs for now
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.