LO goes to `Not Responding` for a specific document

Hello,

Today my wife came to me with the first problem I couldn’t get fixed myself by scanning this forum, or the web in general.

She was working on a document which started from a Word template file. The file is 18 pages long and contains a decent set of images. My wife did not compress these. The resulting file, still in Word format, is 50MB large. At a certain moment, LO crashed on her. When she tried to re-open the document, every time now LO reported (Not Responding) in the application title bar.

When this happened, she was still using LO 7.5.x. I upgraded to 24.2.x, but that made no difference. We opened the Word file in Google Docs, exported to ODT there, but also the ODT variant resulted in (Not Responding).

She is running Windows 11 on an old Lenovo laptop with 8GB RAM. When trying to get this opened, I only had the SurfShark Antivirus running in the background, together with one or 2 Windows Explorer windows.

I have a 32GB MacBook Pro running LibreOffice 24.8.2. Also on my machine, when opening this 50MB Word file, I get the spinning wheel of death.

I’m adding the respective document here in case someone finds this useful for further investigation.

Is there anything I can do on my side to get this document to load succesfully?

Ringo

This is a bug; it is a layout loop on the 1st table in your section 3. I have inserted a page break in front of it, to avoid the loop.

https://drive.google.com/uc?export=download&id=1fuIjW_rpTXYaopP1vRgMrxaafBzXw7NK

tdf#163850

2 Likes

@mikekaganski thanks for the swift reply!

Side question: should my TDF account (used to login here) be usable to login on Bugzilla to subscribe to that issue?

Unfortunately no. Bugzilla is one of the few places which still have not been updated to use the TDF single sign-on system.

1 Like

@mikekaganski is there also another workaround besides a page break? The document is an assignment for the higher education my wife is doing, and she needs to complete it. At the moment, we bump too frequent in these crashes.

Try setting all rows’ heights in tables to fixed values, not automatically expanding.