While exporting a certain document to docx format LibO crashes consistantly. The document had been originally created with LibO. This is unexpected since I have exported many complex documents with good results. A stripped down, almost empty document is attached. Exporting to rtf also crashes. Exporting to doc will quickly eat up your memory causing a linux OS (Kubuntu) to lock up and force you to hard reset. On windows I had some time to terminate LibO. !! warning, you might want to close all other apps before trying to save this as doc on linux and keep systemmonitor or similar ready to kill LibO before it's too late Using the original problematic doc, I tried earlier versions of LibO (back to a windows version 3.6) showing the same behavior. So this seems to be not a regression. As far as I can tell the problem is related to the manual page break, but I have not been able to find the root cause. The original document had multiple pages, large bitmaps and tables. These have been removed in the test document. I have finally been able to export that by removing all manual breaks and inserting a 'page break before' in the Kop 1 (heading 1) style. I have marked this issue severity as major due to the problem potentially causing your machine to lock up.
Created attachment 107218 [details] sample document showing the problem carefull when saveing this to doc see #1
Confirmed with Version: 4.4.0.0.alpha0+ TinderBox: Win-x86@39, Branch:master, Time: 2014-10-03_00:31:27 When I tried to save as DOC, this file quickly ate up RAM and I had to terminate soffice.exe. DOCX also hung when saving.
http://cgit.freedesktop.org/libreoffice/core/commit/?id=f0859c4eae0f567393811c308074723329f1faab
@Caolán: great that you resolved the issue. Would you care to elaborate what was the problem? I fail to understand why if I remove the manual break and add breaks in the H1 style the problem disappears.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.