Looks the same issue as in tdf#160303

For me already REPRODUCIBLE with Installation of Version: 7.6.4.1 (X86_64) 
Build ID: e19e193f88cd6c0525a17fb7a176ed8e6a3e2aa1
CPU threads: 12; OS: Windows 10.0 Build 19045; UI render: default; VCL: win
Locale: Locale: de-DE (de_DE); UI: de-DE; Theme: Automatic (Colibre)
Calc: CL threaded – Normal User Profile

Additional Info: 
----------------
a) Does not matter whether Skia is aktive or not.
b) Currently here only confirmed with WIN
c) DUP: some more observations required

c1) Bug 160303 - Table layout loop in complex table structure after paste RTF:
    NOT reproducible vor me with Installation of Version: 7.6.4.1 (X86_64) 
    Build ID: e19e193f88cd6c0525a17fb7a176ed8e6a3e2aa1
    CPU threads: 12; OS: Windows 10.0 Build 19045; UI render: default; VCL: win
    Locale: Locale: de-DE (de_DE); UI: de-DE; Theme: Automatic (Colibre)
    Calc: CL threaded – Normal User Profile
    Skia on/of does not matter

    So this one might be concerning something different from Bug 160303

Throws a continuous stream of: warn:sw.layout:6444:6360:sw/source/core/layout/wsfrm.cxx:3084: footnote frame on different page than ref frame?

@Stragu
Should we mark this as a duplicate of bug 160303. It's for 99,5% the same file. The major difference is the strategy to trigger the bug.  

There a couple of bug in the bug tracker point to the same underlying issue

https://bugs.documentfoundation.org/buglist.cgi?quicksearch=%22footnote%20frame%22&list_id=1725928

There are likely even more. However I don't know to to search attachments (backtraces) attached by Julien Nabet without over asking search

I can reproduce bug 160303 in a current daily build on Linux, but not your comment 0. On Windows 11, I can reproduce comment 0 - only when two pages are visible side-by-side.
Let's keep separate for now, with this one Windows-specific.
(although I remember another report in which two pages side-by-side was a prerequisite too, we should link to it...).

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