Created attachment 117400 [details] 4.54GB RAM still rising I have a document which I've been opening before without any problems, a file converted from multimarkdown to FODT, about 300kb in total. I tried opening it in 5.0.0.3 and it causes a full hang of writer, the GUI becomes fully unresponsive and it slowly keeps increasing its memory (I saw 33.8GB the first time I checked). It has images but they are referenced from the same directory. The same document opens fine in 4.4.4 — I can't attach as it is confidential. Not sure how I can debug this.
I tried converting from FODT to ODT in 4.4.4 but the ODT also causes the hang.
Created attachment 117402 [details] reduced testcase here is a reduced testcase, this causes a full hang on my libreoffice 5.0.0.3 and 5.1dev -- my OS is OS X 10.11
Created attachment 117403 [details] testcase odt here is a reduced testcase, this causes a full hang on my libreoffice 5.0.0.3 and 5.1dev, but opens fine on 4.4.4 -- my OS is OS X 10.11
Created attachment 117417 [details] Simpler testcase flat odf A even more reduced test case...
I've tested 4.4.5 and it is opening these documents fine...
Not reproducible for me with LibreOffice 5.0.1.0+ built at home under Ubuntu 15.04 x86-64 with gcc 5.1. Tested with both test files. What about if you insert the images in the document instead of keeping them linked? What is your hardware? Intel 64 bits, I presume? Best regards. JBF
I actually just removed the linked image and resaved the document in 4.4.5 and it still crashes 5.1 — I also tried removing the image by editing the XML (removing the paragraph>frame etc around the image too). I left 5.1 while I went for dinner and it hit 63.61GB RAM use (I have 8GB physical RAM), causing several other apps to hang. I can generate a sample using activity monitor, but as you don't have many OS X developers it may be of little use? Hardware is a 2010 Macbook Pro with a core i5 64bit CPU (LibreOffice only has 64bit builds for OS X I think).
Created attachment 117427 [details] testcase removing linked image remove the linked image, simplifying the testcase and still resulting in a 100%CPU and >60GB RAM hang.
Created attachment 117428 [details] sample sample of activity during the 100% CPU hang.
*** This bug has been marked as a duplicate of bug 92898 ***