No repro with
Version: 6.3.0.0.beta1+ (x86)
Build ID: 5cfac16dbd4af456a7fb6d52c8953c69a72ba2ba
CPU threads: 4; OS: Windows 6.3; UI render: GL; VCL: win; 
Locale: nl-NL (nl_NL); UI-Language: en-US
Calc: CL

Created attachment 162266 [details]
Example file

Reproduced in:

Version: 7.1.0.0.alpha0+
Build ID: 10129e2dfc582915d999e24deed34f7303a6f02e
CPU threads: 6; OS: Linux 5.4; UI render: default; VCL: gtk3
Locale: hu-HU (hu_HU.UTF-8); UI: en-US
Calc: threaded

No repro

Version: 7.1.0.0.alpha0+ (x64)
Build ID: 8fe03ea93213bbb19b6ee9862a3966144f0df5cb
CPU threads: 4; OS: Windows 10.0 Build 18362; UI render: Skia/Raster; VCL: win
Locale: fi-FI (fi_FI); UI: en-US
Calc: threaded

(In reply to Buovjaga from comment #4)
Still the same
Version: 7.1.0.0.alpha0+ (x64)
Build ID: 006c65bbd472cb1d7d44e095714e28190b76be0d
CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: default; VCL: win
Locale: nl-NL (nl_NL); UI: en-US
Calc: CL

@Buovjaga.. do you also have throttle button on you're powerful machine. Maybe it's some kind of race condition .. And your computer is just to fast to hit it

I could reproduce it. 
Version: 7.3.0.0.alpha0+ / LibreOffice Community
Build ID: 5aac78e5fb241050a86714687e9ff8804588ae3c
CPU threads: 12; OS: Mac OS X 10.15.7; UI render: default; VCL: osx
Locale: en-GB (en_GB.UTF-8); UI: en-US
Calc: threaded

I could reproduce it, when I pressed enter over 20X.
Version: 7.0.6.2
Build ID: 144abb84a525d8e30c9dbbefa69cbbf2d8d4ae3b
CPU threads: 12; OS: Mac OS X 10.15.7; UI render: default; VCL: osx
Locale: en-GB (en_GB.UTF-8); UI: en-US
Calc: threaded

Bibisected with linux-64-6.4 to
https://git.libreoffice.org/core/commit/383032c50a3e3354f04200ce984a47ab9d2c5c67
tdf#123583 use TaskStopwatch for Writer Idle loop

Adding Cc: to Jan-Marek Glogowski

FYI: the bibisect commit was reverted to fix bug 141556 in 
https://git.libreoffice.org/core/+/0fedac18214a6025401c4c426466a5166553e8ec%5E%21

I tried to find an alternative fix (dropping quite some code), but everything I came up with resulted in broken layout: https://gerrit.libreoffice.org/c/core/+/114105

Main problem is that I simply don't understand the condition, when it's actually fine to break the layout, so it can be resumed correctly. 2nd problem is, that the idle layout is currently stateless, but for my current approach it would need some state to handle removing of pages.

So I'm removing the bibisect* keywords; maybe it can be bibisected again hoping for a better result.

(In reply to Jan-Marek Glogowski from comment #8)
> FYI: the bibisect commit was reverted to fix bug 141556 in 
> https://git.libreoffice.org/core/+/
> 0fedac18214a6025401c4c426466a5166553e8ec%5E%21
> 
> I tried to find an alternative fix (dropping quite some code), but
> everything I came up with resulted in broken layout:
> https://gerrit.libreoffice.org/c/core/+/114105
> 
> Main problem is that I simply don't understand the condition, when it's
> actually fine to break the layout, so it can be resumed correctly. 2nd
> problem is, that the idle layout is currently stateless, but for my current
> approach it would need some state to handle removing of pages.
> 
> So I'm removing the bibisect* keywords; maybe it can be bibisected again
> hoping for a better result.

I don't see how it could be bibisected again as 0fedac18214a6025401c4c426466a5166553e8ec makes no difference to the result. Do you mean bibisecting earlier than 6.4? What would be the good/bad states?

(In reply to Buovjaga from comment #9)
> (In reply to Jan-Marek Glogowski from comment #8)
> > FYI: the bibisect commit was reverted to fix bug 141556 in 
> > https://git.libreoffice.org/core/+/
> > 0fedac18214a6025401c4c426466a5166553e8ec%5E%21
> > 
> > I tried to find an alternative fix (dropping quite some code), but
> > everything I came up with resulted in broken layout:
> > https://gerrit.libreoffice.org/c/core/+/114105
> > 
> > Main problem is that I simply don't understand the condition, when it's
> > actually fine to break the layout, so it can be resumed correctly. 2nd
> > problem is, that the idle layout is currently stateless, but for my current
> > approach it would need some state to handle removing of pages.
> > 
> > So I'm removing the bibisect* keywords; maybe it can be bibisected again
> > hoping for a better result.
> 
> I don't see how it could be bibisected again as
> 0fedac18214a6025401c4c426466a5166553e8ec makes no difference to the result.
> Do you mean bibisecting earlier than 6.4? What would be the good/bad states?

No. I thought it may have been fixed by 0fedac18214a6025401c4c426466a5166553e8ec and then broken again after it and you just unluckily skipped that in the bibisect. My assumption is that 0fedac18214a6025401c4c426466a5166553e8ec is ok, as it's a revert.

OTOH, while it technically reverts my commit, it also includes new code to fix the original problem. So you can test 0fedac18214a6025401c4c426466a5166553e8ec, but if that is still broken, you need to rule out, that the new code introduces this, which would mean to build LO at that commit and just revert the new part; that's a lot of work...

Or maybe it's enough to just revert that new code part on master.

(In reply to Jan-Marek Glogowski from comment #10)
> No. I thought it may have been fixed by
> 0fedac18214a6025401c4c426466a5166553e8ec and then broken again after it and
> you just unluckily skipped that in the bibisect. My assumption is that
> 0fedac18214a6025401c4c426466a5166553e8ec is ok, as it's a revert.
> 
> OTOH, while it technically reverts my commit, it also includes new code to
> fix the original problem. So you can test
> 0fedac18214a6025401c4c426466a5166553e8ec, but if that is still broken, you
> need to rule out, that the new code introduces this, which would mean to
> build LO at that commit and just revert the new part; that's a lot of work...
> 
> Or maybe it's enough to just revert that new code part on master.

In my comment 9 I should have mentioned that I checked out and tested 0fedac18214a6025401c4c426466a5166553e8ec in 7.2 repo

I will try manually reverting later today and compiling

I reverted the new bit, but unfortunately the problem remains :(

Git diff of what I changed:

diff --git a/sw/source/core/inc/layact.hxx b/sw/source/core/inc/layact.hxx
index a0f955aa4099..a0f84d720a67 100644
--- a/sw/source/core/inc/layact.hxx
+++ b/sw/source/core/inc/layact.hxx
@@ -21,7 +21,6 @@
 
 #include <sal/config.h>
 
-#include <vcl/inputtypes.hxx>
 #include <tools/color.hxx>
 
 #include <ctime>
diff --git a/sw/source/core/layout/layact.cxx b/sw/source/core/layout/layact.cxx
index 95a48df5efda..e5edd93cee58 100644
--- a/sw/source/core/layout/layact.cxx
+++ b/sw/source/core/layout/layact.cxx
@@ -39,7 +39,6 @@
 #include <sfx2/event.hxx>
 
 #include <ftnidx.hxx>
-#include <vcl/svapp.hxx>
 #include <editeng/opaqitem.hxx>
 #include <SwSmartTagMgr.hxx>
 #include <sal/log.hxx>
@@ -2246,7 +2245,7 @@ SwLayIdle::SwLayIdle( SwRootFrame *pRt, SwViewShellImp *pI ) :
         bool bInterrupt(false);
         {
             SwLayAction aAction( m_pRoot, m_pImp );
-            aAction.SetInputType( VCL_INPUT_ANY & VclInputFlags(~VclInputFlags::TIMER) );
+            aAction.SetInputType( VCL_INPUT_ANY );
             aAction.SetIdle( true );
             aAction.SetWaitAllowed( false );
             aAction.Action(m_pImp->GetShell()->GetOut());

(In reply to Jan-Marek Glogowski from comment #8)
> Main problem is that I simply don't understand the condition, when it's
> actually fine to break the layout, so it can be resumed correctly. 2nd
> problem is, that the idle layout is currently stateless, but for my current
> approach it would need some state to handle removing of pages.

Is this not simply some layout issue, where table rendering keeps forcing a frame union. Which for some reason not 'passed' based on timing? 

I see this more as an uncovered table splitting bug. Where certain kind of frame union is tried, but failing (oscillating back and forward) without a bail-out (likely because embedded table in table)

The bail-out obviously result in some layout change, but if it's the same prior 6.4, who cares? Layout loop seems more evil to me ;-)

Dear Telesto,

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
 
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug