Created attachment 107871 [details]
Attached MS file
Facing difficulty in opening huge files no matter if its impres/calc/writer. The base files are created in Ms office(opens within a sec in MS office). Attaching the file. Appreciate your response.
Tested with all the versions of Libre office. Using windows platform.
I was able to open it on 4.3.3 and master, though it took a bit of time to open, it did open after 2 or so minutes. How long does it normally take for you?
It takes more than ten mins to load half through but never opens. We tried with version 184.108.40.206. Pls advice.
give exact details of your O/S and CPU
Created attachment 107910 [details]
CPU details 1
Created attachment 107911 [details]
Attached 2 screenshots of different PC.
Can you tell me if you opening the same file in windows platform or anyother platform. After too many trys we tried the same file to open with openoffice it opened immediately. Any views on this.
My previous test was on Linux Mint 13 32-bit.
I just tested 3.3.0, 3.6.7, 4.3.2 and master on Windows 7 64-bit and i cancelled trying to open the file after 5 minutes. The loading progress bar goes to around 60% and not any farther. Tried doing a backtrace but with no luck.
Right we have no clue why we are unable to open. We tried to open the same file in Open office 3.4.1 it opens without any issues.
AOO 4.1: 3 seconds
LO 4.4: > 3 minutes with single core running at 100%
@Michael: Any ideas on how i can track down what is going wrong on Windows.
Waited 40 minutes to see if the file would open under Windows, but no luck.
Even if you wait for an day it wont open..... Even other libre files cannot be opened.
Oh fun - just get a few stack traces during the load; it'll show the problem nicely I guess; odd though - I don't see any huge changes in our automated performance testing, so ... at least our test files are still loading nice & quickly there =) then again - we limit the size of those.
Seems to be spending a lot of time re-saving the embedded objects as ODF etc. and ... Hmm. not good.
Jay - I suspect that changing the defaults:
around embedded objects [ we always convert them - otherwise they will not be editable ;-) - and I think AOO just leaves them as-is ].
This is a horrible false-dichotomy that shouldnt' exist; we should convert them as/when we need to on activation / macro use etc. but ... it is there.
Can you compare AOO with those options set.
Also - is this really a regression ? some big files that have not been optimised are slow - that's not really news =)
Judging by the debug output, one problem is that we may be spending a long time failing to load referenced smb:// objects. The document appears to contain quite a few such references
(In reply to Michael Meeks from comment #13)
> Oh fun - just get a few stack traces during the load; it'll show the problem
> nicely I guess; odd though - I don't see any huge changes in our automated
> performance testing, so ... at least our test files are still loading nice &
> quickly there =) then again - we limit the size of those.
The problem here wasnt really the size of the file, so doubt it would effect any of the automated testing. ;D
> Seems to be spending a lot of time re-saving the embedded objects as ODF
> etc. and ... Hmm. not good.
> Jay - I suspect that changing the defaults:
> Tools->Options->Load/Save->Microsoft Office
> around embedded objects [ we always convert them - otherwise they will not
> be editable ;-) - and I think AOO just leaves them as-is ].
Yes OpenOffice has these checkboxes unchecked and after unchecking them on LO, the file opened in 10 to 20 seconds on Windows. But what seems strange is that the file doesnt load on Windows with these checked, but loads on Linux with them checked.
> This is a horrible false-dichotomy that shouldnt' exist; we should convert
> them as/when we need to on activation / macro use etc. but ... it is there.
> Can you compare AOO with those options set.
With checking these options in AOO, the file loads in > 4 minutes on Linux.
> Also - is this really a regression ? some big files that have not been
> optimised are slow - that's not really news =)
Well as this change was introduced in the first release of LO, then i wouldnt consider it a LO regression. :D
I did tried to uncheck the embedded options and the files load quickly and accessible. So now how do we conclude the resolution. Please advice.
Well - it's an enhancement really; I hope there is another tracker enhancement for deferring the work here until embedded objects are activated; this whole idea of that setting is a global embarrassment ;-) we should "do it right".
It'd be nice to look for that enhancement to mark this one as being blocked by it - if you can (?)
Filed it - bug 85364.
(This is an automated message.)
LibreOffice development currently prioritizes bugs with the so called MAB (most annoying bugs) -- as this bug has not run through that process (including writing a short rationale for this bug being a candidate and other who are watching the tracker bug silently approving that rationale etc.) its priority is set to high. Note this is effectively no change in the urgency assigned to this bug, as we are currently not making a difference between high and highest and severity is untouched.
You can find out more about MABs and how the process works by contacting libreoffice qa on irc:
The QA wiki page also gives you hints on how to get in contact with the team (if IRC fails you, your next best choice is the mailing list):
Migrating Whiteboard tags to Keywords: (filter:ppt, perf)
Build ID: 690f553ecb3efd19143acbf01f3af4e289e94536
CPU Threads: 4; Versie besturingssysteem:Windows 6.2; UI Render: standaard; Layout Engine: new;
Locale: nl-NL (nl_NL); Calc: CL
convert with MS Office (my version 2010) in pptx
than import in LOO (my Version 5.2.7) successful
Created attachment 133263 [details]
converted pptx with MS Office 2010
converted pptx of ppt bug file with MS Office 2010
successful import with LOO 5.2.7
Documents won't load. No visible text or graphics.
Aron: Maybe one for the weekend. ;D
Still reproducible in
Build ID: a1f93eee75450c3ab6bc623bfad4f850260b86d0
CPU threads: 1; OS: Windows 6.1; UI render: default;
Locale: fr-BE (es_ES); Calc: group
** 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!
Created attachment 151057 [details]
On pc Debian x86-64 with master sources updated today + enable-symbols and without debug, I could reproduce this.
Still unable to open on Win
Version: 220.127.116.11.alpha0+ (x64)
Build ID: e1b51d4588b4b39592bb94dd5bb90de5e04d061e
CPU threads: 4; OS: Windows 10.0; UI render: default; VCL: win;
TinderBox: Win-x86_64@62-TDF, Branch:master, Time: 2019-09-23_09:16:11
Locale: fi-FI (fi_FI); UI-Language: en-US