Description: I have a 6 page "Will" document, did some experimenting to see what works/doesn't since my busted up password protected document -only- takes 2 minutes to open: 1. [works] OpenOffice 4.1.3 (Windows) Opens the 6 page document almost instantly. 2. [works] Using OpenOffice 4.1.3 to do a "SaveAs..." to a new filename, with same or new password, creates a document which LibreOffice x64 (5.x, 6.x) will open quickly. (Yes, this is a "recovery tactic") 3. [doesn't] Waiting for LibreOffice to open the offending document and then using LibreOffice to perform a "SaveAs..." just makes another "broken file" and takes twice as long to do as opening the "broken file", 1x to SaveAs... + 1x to get LibreOffice "unhung" so it will close. Behavior under Ubuntu 16.04 LTS and Windows 10 x64 is the same. soffice.bin uses 100% of 1-CPU while performing it's shenanigans. Under Windows 10 x64 it just says LibreOffice "Not responding" until the file actually opens ~ 2minutes later. Windows LibreOffice v5.4.3.2 x64, and 6.0.5 x64 Ubuntu 16.04 LTS x64 v5.1.6.2 Observations: a) The META-INF/Manifest.xml produced by #2 above is quite different from the original file with all the problems. This different META-INF/Manifest.xml seems to work well with LibreOffice 5.x/6.x x64 on both Linux and Windows Platforms. b) The META-INF/Manifest.xml produced by #3 matches the original file which causes all the problems on opening. c) My file having all the problems was created using LibreOffice and is timestamped 27-Aug-2016. I tend to keep LibreOffice up to date so it was produced using a "current version" around that date. d) It's -really- nice to have an OpenDocument -STANDARD- for ODT type files so other tools can be used for just such occasions. Who knows, maybe next time OpenOffice will be the one experiencing problems. At least we have choices about what to try. The OpenOffice site, in case you forgotten, is http://www.openoffice.org/ This should help you recover your documents so you can continue to use LibreOffice. Actual Results: Document hangs LibreOffice for 2 minutes on Linux and Windows 10. On both systems the Window and task become unresponsive for 2 minutes. Expected Results: Like OpenOffice 4.1.3, I expect a document of this complexity to open in about 1 second.AOO413m1(Build:9783) - Rev. 1761381 Reproducible: Always User Profile Reset: No Additional Info: Since this is a financial document containing account names and passwords with occasional bitmap images, it can't be posted here. A first crack at "sanitizing" this document made the problem go away. Instead, I'll post the META-INF/manifest.xml from the file which doesn't work and the one that does, since this difference is noted and is significant. Since I'm also posting a way to recover the file with this condition, I hope this will do. OpenGL doesn't appear to be used, LibreOffice is calling it OpenCL. Allowing the use of "OpenCL" doesn't make any difference. Version: 5.1.6.2 Build ID: 1:5.1.6~rc2-0ubuntu1~xenial3 CPU Threads: 8; OS Version: Linux 4.4; UI Render: default; Locale: en-US (en_US.UTF-8); Calc: group Version: 5.4.3.2 (x64) Build ID: 92a7159f7e4af62137622921e809f8546db437e5 CPU threads: 4; OS: Windows 6.19; UI render: default; Locale: en-US (en_US); Calc: group https://gerrit.libreoffice.org/gitweb?p=core.git&a=log&h=92a7159f7e4af62137622921e809f8546db437e5
Created attachment 143740 [details] META-INF/manifest.xml from ODT with problems This META-INF/manifest.xml file is from the password protected ODT file which causes the ~2 minute opening delay under both Linux and Windows.
Created attachment 143741 [details] META-INF/manifest.xml from the "good" document, produced by OpenOffice This META-INF/manifest.xml file is from the password protected ODT file which opens nearly instantly under both Linux and Windows. Content is visually the same in both Good and Bad documents.
you should provide that file, otherwise it will be impossible for us to test and debug. if it has condidential data you have to anonymize it somehow and post it here NEEDINFO
Normally we wait with Needinfo until reporter responds. But you said: "Since this is a financial document containing account names and passwords with occasional bitmap images, it can't be posted here. A first crack at "sanitizing" this document made the problem go away." So I'll close. If you have reproducible steps and example document, please set back to Unconfirmed. And please see Bug 105844.