https://bugs.documentfoundation.org/show_bug.cgi?id=153692
Buovjaga <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ilmari.lauhakangas@libreoff | |ice.org Keywords|bibisectRequest | --- Comment #3 from Buovjaga <[email protected]> --- (In reply to Telesto from comment #1) > also in > Versie 4.0.0.3 (Bouw-id: 7545bee9c2a0782548772a21bc84a9dcc583b89) No coherent result here. A state in older versions is that there is already an empty space at the bottom of the page with 45:45. However, if I jump to this page immediately after opening, I can see the empty space does not yet exist. It appears after layouting is complete. In Linux 43max I can see states with this empty space, but sometimes even in the same commit it might be layouted without the empty space and staying like that consistently. Yet it can crash upon undoing the row deletion. This crashing continues in 44max. I noticed in linux-64-5.2 repo the oldest has an empty space on the page, jumps after undo, but otherwise retains the layout. The master did not have an empty space initially, jumped and then had the empty space after undo. Apparently this started with commit 905e38c7c6c02ec618b9231545c45debba3a8a44 Author: Michael Stahl <[email protected]> Date: Thu Jun 9 15:52:16 2016 +0200 tdf#96089 sw: fix scope of bBreakAfter in InsertCnt_() The problem is that bBreakAfter is passed by reference to SwLayHelper and stored as a reference member there, so it has to live at least as long as pPageMaker. (Unfortunately C++ can't statically check that.) This then somehow caused the number of pages created after initial load to be 812 instead of the correct 396 determined from the layout-cache in the bugdoc, and that then caused Drawing objects to move backward during the following re-pagination, and then SwDrawContact::Changed_() calls SetFlyFrmAttr() and that sets the document to modified, which triggers the AutoSave that was reported in the bug. (regression from b4b7703e4335460cf48bfd6440f116359994c8ff) The history is so messy that I will not add keywords. -- You are receiving this mail because: You are the assignee for the bug.
