Reproducible
Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: c9d4f99b2bb54ac7735b3e0d0cadbafbd0279518
CPU threads: 16; OS: Windows 10.0 Build 22631; UI render: default; VCL: win
Locale: es-ES (es_ES); UI: en-US
Calc: CL threaded

Crash at opening with
Version: 24.2.2.2 (X86_64) / LibreOffice Community
Build ID: d56cc158d8a96260b836f100ef4b4ef25d6f1a01
CPU threads: 16; OS: Windows 10.0 Build 22631; UI render: Skia/Raster; VCL: win
Locale: es-ES (es_ES); UI: en-US
Calc: CL threaded

I have tried to resave with Word but no success, still crash at opening.
Added crash report signature.

Regarding the fileopen crash:

(m_a_riosv, your crash report https://crashreport.libreoffice.org/stats/crash_details/2aae081f-3599-4d36-9506-8365850dac7b doesn't lead to anything, not sure why.)

I also get a crash on open in 7.6.6.3 and 24.2.2.2: https://crashreport.libreoffice.org/stats/crash_details/209449ce-fa0d-4f03-98cb-05e6716f9a7c
(same signature ["SwTabFrame::MakeAll(OutputDevice*)"] as for bug 158344)
...but it is fixed in master. In linux-64-24.8, it stopped crashing at build [ba26d9d81765ca45f3e8383714cf2b8eb077c07f] which is:

commit 186de7178c6065e1de13fd216b46ac9b716e44c5
author	Miklos Vajna 	Thu Feb 29 08:17:41 2024 +0100
committer	Miklos Vajna 	Thu Feb 29 11:39:54 2024 +0100
tdf#158801 sw floattable: fix crash with headers and interactive editing
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/164136

The cherrypick to 24.2 hasn't been merged yet: https://gerrit.libreoffice.org/c/core/+/164119

@miklos, you'd rather not get that in 7.6 because https://gerrit.libreoffice.org/c/core/+/163805 is not cherrypicked to that branch, correct?

---

Regarding the font size crash:

I reproduce in a recent trunk build too. It already crashes at the above quoted commit.

Created attachment 193479 [details]
bt with console logs

On pc Debian x86-64 with master sources updated today, I could reproduce this.

Layout pb according to the bt.

> @miklos, you'd rather not get that in 7.6

Writer layout patches are always a bit risky, so at this point it's probably useful if floating table commits are only backported to 24.2 and not further. But as you like. :-) My suggestion was just that if a backport happens, then you don't selectively pick a specific fix, but all fixes up to that fix should also be backported, since I always just test master with and without a fix, not out of order fixes.

(In reply to Miklos Vajna from comment #4)
And that's perfectly understandable, happy to go with your preference here if the chain of fixes is too hairy to backport :)

Just noting that this document's fileopen:

- started freezing in in 7.6.1 at 7278c1facfd675dd1972a01370de4425704d9a16
- started crashing in 7.6.2 at 9e453a7af284cf17cb0debd2ab027f626e6e4a62

But given that the signature is quite rare (9 reports currently), we can assume it doesn't affect many users, so let's just stick to 24.2 fixes: https://crashreport.libreoffice.org/stats/signature/SwTabFrame::MakeAll(OutputDevice*)

Let's focus on the font size change crash then, targetting 24.2 and trunk!

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