Writer freezes opening documents with external images created in MS Word

I’m using LibreOffice to generate PDF previews for docx files.

Tested on Ubuntu 25.04, 25.10, AWS Linux 2023.
Versions from 7.x to 25.8.1.1

The problem is always the same, document contains content pasted from internet, in my case it is private information from banks either email or a web page.

Writer hangs trying to open such document.

Is there any way to debug or fix this? I can not understand why it happens.

Calc keeps hanging and crashing (provisional) - #2 by fpy

I’ve tried safe mode - the same result, writer hangs.

I also tried to set invalid proxy to make sure it’s not related to slow image loading, and it makes no difference.

If the document is a private one of yours, not intended for public release, why do you save .docx? Does it happen with native .odt format?

Can you prepare a non-confidential document with the same issue and attach it here?

it’s not mine, if I could I’d attach it, it contains private information. People are used to ms word and simply copy & paste web content there, I have no control over this.

When people change their cars from an Otto engine to a Diesel one, do they keep the same fuel? Obviously no because they know this could lead to damage. You should educate them: for any application, save in native format. Or else, they must hire (and pay for) the application they are used to.

Without a sample file, it is extremely difficult to venture a diagnostic hypothesis.

ok, I removed links and text and reassembled document:
sample_hangs.docx (65.9 KB)

Filed a bug 170391.

1 Like

When I try to open your sample, a window frame briefly appears, then nothing. CPU activity reaches 99.7% and I must kill the process.

Looking at the contents, the document seems to have a complex structure with a table and a lot of drawing shapes. I see “references” to pictures as name="Picture xx" but this “name” does not match the image file names kept in the document. The xx itself does not correspond to file numbering. There are numerous links to “http://schemas.openxmlformats.org/…” and “http://schemas.microsoft.com/office/…” but I am not familiar with M$ encoding to tell if there is an access issue.

There is even an image directly embedded as a Base64 byte blob.

The only text I can make out is “Links contained in this email have been replaced. […] you will see a warning.

are they first told it’s compatible ? :face_with_thermometer:

What is LibreOffice? | LibreOffice - Free and private office suite - Based on OpenOffice - Compatible with Microsoft
image

big questions : who are “you” and who are “them” :confused:

would be nice to escalate to Marketing | LibreOffice - Free and private office suite - Based on OpenOffice - Compatible with Microsoft

good practice is then to set the bug status to NEW. see https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status#How_to_select_the_correct_bug_status

luckily someone else did it, and followed up with https://wiki.documentfoundation.org/QA/Bibisect to spot the regression.