Created attachment 126247 [details]
its a .doc document which its content is in farsi and arabic.
i have a large .doc document with 960 pages when openning in libreoffice writer.
my document content is in farsi and arabic and its size is more than 9 mb.
every time i want to open it with libreoffice writer, it needs one hour and 45 minutes for me to open!
i use windows xp, but my sister tested with windows 7.
for her, the document opened after one hour and 15 minutes.
i tested this document with microsoft word and nvda screen reader says protected document.
i opened it with microsoft word in seconds!
i tested with openoffice 4.1.2 and it took 40 minutes to open it.
while, i have a .doc book with more than 2000 pages opened in libreoffice only with 15 minutes!
and also another .doc document like this, with only 39 pages which needs 15 to 20 minutes.
i dont understand the reason of many many different times in openning my document!
i appreciate your help to know the reason.
*** Bug 100968 has been marked as a duplicate of this bug. ***
confirmed on recent master 2016-07-16
note: small test cases are preferred
if you have a one page document which loads in half a minute with LO instead of a second in Word, that would be great.
Using odt to save, works fine, only a few seconds to open.
Cleaning all direct format open just fine saving/reopening as doc.
As I remember for other bugs and threads in forums, LibreOffice doesn't like too much an intensive use of direct format, importing ms files.
So perhaps, cleaning direct format and setting up properly default format can reduce the need for a hard use of direct format.
Setting to NEW. Confirmed slowness here as well.
Arch Linux 64-bit, KDE Plasma 5
Build ID: 64d3270a89fd88d4d0cf70329af2c66f722fd95e
CPU Threads: 8; OS Version: Linux 4.6; UI Render: default;
Locale: fi-FI (fi_FI.UTF-8); Calc: group
Built on July 22nd 2016
Created attachment 126393 [details]
Callgrind with 5.3
Got a callgrind of opening the file.. it took about 30 hours.
my documents all of them more than 200 pages and i dont have a document but with the same structure with this one.
thanks so much and God bless you.
** Please read this message in its entirety before responding **
To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.
There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.
If you have time, please do the following:
Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/
If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.
Please DO NOT
Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not
appropriate in this case)
If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/
2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword
Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa
Thank you for helping us make LibreOffice even better for everyone!
i tested my book with my favorite version of libreoffice (188.8.131.52) and the issue persists.
one hour and 45 minutes for openning the file, with 2gb ram and cpu Genuine Intel(R) CPU T2250 @ 1.73GHz
Same problem here with 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.
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.
Craig: your issue is a different one. As zahra mentioned, AOO is slow for this particular .doc as well.
Please open a new report with your example file attached. If it contains confidential information, create a sanitized copy: https://wiki.documentfoundation.org/QA/Bugzilla/Sanitizing_Files_Before_Submission#Sanitize_file_text