https://bugs.documentfoundation.org/show_bug.cgi?id=157994
Bug ID: 157994
Summary: "Error in writing sub-document content.xml", with
large files, two open at once
Product: LibreOffice
Version: 7.6.2.1 release
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: UNCONFIRMED
Severity: normal
Priority: medium
Component: Writer
Assignee: [email protected]
Reporter: [email protected]
Created attachment 190524
--> https://bugs.documentfoundation.org/attachment.cgi?id=190524&action=edit
main error message
There seem to be many reports here and on the internet about this error, people
seem to have been getting it for over a decade. At least some of the reports of
this error message seem to have been caused by something else, since the
authors claim the problem has been solved for them, other reports have remained
unsolved for years.
I think this is the first time someone has encountered this error and is able
to provide files and steps to actually reproduce it.
My system info: https://pastebin.com/raw/gNFjGpAQ
Libreoffice version:
Version: 7.6.2.1 (X86_64) / LibreOffice Community
Build ID: 56f7684011345957bbf33a7ee678afaf4d2ba333
CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3
Locale: en-US (en_US.UTF-8); UI: en-US
Flatpak
Calc: threaded
I can't share the original files causing this error publicly (of which I have
more than one) and it took hours to create files which can reproduce the issue
reliably, so please be nice.
The example files are exagerrated (too large, images too high res) to ensure
the error will be reproducible, real files are much more sane and will be
described in the end of this description.
Here are two example ODT files:
https://e.pcloud.link/publink/show?code=kZhmesZdfD1h7n0KmVIjk2czH7XK5ueeGVy
(few hundred MB so I couldn't attach here)
The files contain placeholder text and many images from Pixabay.
To reproduce the issue:
1) Open both files. This is critical. If only one file is opened at a time, the
bug doesn't happen.
2) Copy the contents of "test 2.odt" into the last blank page of "test 1.odt".
3) Save "test 1.odt". There is a 50% chance in my case that you will get the
error "error.png" attached here.
4) If the error does not happen, just paste again and save "test 1.odt" again.
In my case there's a 100% chance you'll get the error now. If you won't on your
system, please try pasting and saving few more times.
I've made sure I'm not running out of RAM when this happens.
5) After getting the error, if you'll close the error window and try saving
again, both Libreoffice ODT file windows will simply silently crash and close.
6) If you'll try opening Libreoffice again, it will either silently crash at
the banner (but not the second time), or will launch the recovery wizard like
so: https://i.ibb.co/LPj0mbP/error-2.png
7) If you'll attempt a recovery of "test 1.odt", very likely it will fail like
so but not always: https://i.ibb.co/sFhGkVp/error-3.png
8) Same with "test 2.odt" which it will try to recover next, very likely it
will fail like so but not always: https://i.ibb.co/bdcfqcJ/error-4.png
Here's a real life example of this happening:
I have many research documents with many medium resolution (~1024x1024) images
in them and moderate amount of text. Their sizes range in 100-400MB and each
are at least 50 pages. Often times I need two such documents open at once,
since I need to fill data in both as I work. Sometimes, when adding a text and
a single medium resolution image to one, saving it will cause this error.
I can close the second ODT file before saving to avoid the error, but closing
and reopening the second window seriously slows down my worlflow.
I've been experiencing this bug for around 6 months, it happens randomly. I've
lost many hours of work because of it, by forgetting to save every few minutes.
Sometimes after the crash, if I open the unsaved file, fill it with the same
text and add the same image, it won't crash the second time (even with the
second ODT file open). This is why it's so extremely hard to report this bug
and provide an example file. It's not only the issue of people being unable to
share their original files, but also due to the error requiring large files and
not having very clear steps that always guarantee it will happen.
--
You are receiving this mail because:
You are the assignee for the bug.
