the file: JCTVC-G1103_d9.doc is 226 pages long. I have a core i3 with 4gb ram, the importing progress bar goes towards the end after about 1 minute then the window just stalls. I've left it for 10 mins and it has done nothing, it is using 100% cpu on 1 core.
Created attachment 56739 [details] .doc file hangs when trying to open
here is the .doc file as for some reason it doesn't seem to be letting me upload it properly: http://www.fileserve.com/file/XVfx42S/JCTVC-G1103_d9.doc http://www.mediafire.com/?is9i2t5tn8ss3t9 http://www.filedropper.com/jctvc-g1103d9
Reproduced with LibreOffice 3.5.0rc3 7e68ba2-a744ebf-1f241b7-c506db1-7d53735 Ubuntu 10.04.3 x86 Linux 2.6.32-38-generic Russian UI
this bug is still present in v3.5.1, hope someone can fix this bug soon.
i can open it with 3.5.4.2
This opens with Libreoffice 3.6 beta 1 but it took around 2 minutes to open on a core i5 2.4ghz 6gb laptop.
Checked with: LO 3.5.5.3 Build ID: own W7 debug build Windows 7 Professional SP1 64 bit Could not reproduce the crash. Opening and parsing a file is very slow.
hajj: could you give a try with last LO version (3.6.4)? If you still reproduce this, could you upload the file by following this link? (https://wiki.documentfoundation.org/QA/Bugzilla-Attachments)
I just found out that if you right click my attachment and choose "save as" you will be able to save the file which by default will be called JCTVC-G1103_d9.zip, just extract the .doc file from it. I have tested this JCTVC-G1103_d9.doc file with Libreoffice 3.6.4 and it still loads incredibly slowly, it took around 2 mins and 10 seconds on my core i5 laptop with 6gb ram.
Comment on attachment 56739 [details] .doc file hangs when trying to open fix mimetype
i can only upload it as a .zip on this bug tracker because the .doc file is 226 pages long and 6.62mb once extracted, i have uploaded the .doc file here though: http://www.mirrorcreator.com/files/SE4EMWEY/JCTVC-G1103_d9.doc_links
Created attachment 72552 [details] console logs on master On pc Debian x86-64 with master sources updated today, I reproduced the problem.
Created attachment 72553 [details] some bts at random with master sources some bts too. Hajj: the only problem with the attachment was the mimetype. It was "text/html" instead of "application/zip" Thank you for your feedback.
Cedric/Michael: one for you?
This takes approximately 3mins 25secs with Libreoffice 4.0 beta 2 btw. 1 minute 15secs longer than v3.6.4. I hope you can fix this in v4.0 final as well as 3.6.x.
This opens very slow on OS X as well. Setting platform to All. Crashed LO 4.1.1.2 and LO Version: 4.2.0.0.alpha0+ Build ID: f4d3954fc6106b3ae0ee16ab0fcde15d8cb945e3 for me.
Restricted my LibreOffice hacking area
For the record, on pc Debian x86-64 with master sources updated today, I can still reproduce this. I noticed these console logs: warn:sot:2797:1:sot/source/sdstor/stgdir.cxx:424: Trying to resize readonly stream by seeking, could be a wrong offset: 2617461 warn:sot:2797:1:sot/source/sdstor/stgdir.cxx:424: Trying to resize readonly stream by seeking, could be a wrong offset: 2616987 warn:sot:2797:1:sot/source/sdstor/stgdir.cxx:424: Trying to resize readonly stream by seeking, could be a wrong offset: 2616987 warn:sot:2797:1:sot/source/sdstor/stgdir.cxx:424: Trying to resize readonly stream by seeking, could be a wrong offset: 2617461 warn:sot:2797:1:sot/source/sdstor/stgdir.cxx:424: Trying to resize readonly stream by seeking, could be a wrong offset: 2616987 warn:sot:2797:1:sot/source/sdstor/stgdir.cxx:424: Trying to resize readonly stream by seeking, could be a wrong offset: 2617461
** 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 on a currently supported version of LibreOffice (5.1.5 or 5.2.1 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) 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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20160920
This bug is still present in Libreoffice 5.2.1 x64 on windows 10 x64.
Reproducible with Version: 5.4.0.0.alpha0+ Build ID: a9f56091b6422ec8c42f09b8472200ae4ab12548 CPU Threads: 4; OS Version: Windows 6.19; UI Render: default; TinderBox: Win-x86@42, Branch:master, Time: 2016-12-05_23:12:26 Locale: nl-NL (nl_NL); Calc: CL
** 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! Warm Regards, QA Team MassPing-UntouchedBug
Bug still present in latest version. Version: 6.0.5.2 (x64) Build ID: 54c8cbb85f300ac59db32fe8a675ff7683cd5a16 CPU threads: 4; OS: Windows 10.0; UI render: GL; Locale: en-GB (en_GB); Calc: group
Dear spaceshipgalore, 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! Warm Regards, QA Team MassPing-UntouchedBug
This bug is still present in v7.0.3.1 x64 (tested on win 10 x64)
i forgot to add the details: Version: 7.0.3.1 (x64) Build ID: d7547858d014d4cf69878db179d326fc3483e082 CPU threads: 4; OS: Windows 10.0 Build 19042; UI render: Skia/Raster; VCL: win Locale: en-GB (en_GB); UI: en-GB Calc: threaded
this problem still exists in v7.3.0: Version: 7.3.0.3 (x64) / LibreOffice Community Build ID: 0f246aa12d0eee4a0f7adcefbf7c878fc2238db3 CPU threads: 4; OS: Windows 10.0 Build 19044; UI render: Skia/Vulkan; VCL: win Locale: en-GB (en_GB); UI: en-GB Calc: CL
3.5m 12,33s user 0,94s system 86% cpu 15,30 total (not good looking) 3.6m 61,25s user 1,30s system 93% cpu 1:06,56 total 4.0m 135,22s user 1,96s system 97% cpu 2:20,92 total 4.2m 88,05s user 1,51s system 88% cpu 1:40,80 total 4.4m 88,05s user 1,75s system 80% cpu 1:51,39 total 5.0m 100,12s user 1,48s system 97% cpu 1:44,62 total 5.1m cannot open 5.2m 264,02s user 1,74s system 91% cpu 4:49,15 total 6.2m 302,53s user 1,32s system 92% cpu 5:28,06 total 7.2m >10 7.4+ 05,48s user 2,35s system 93% cpu 7:16,98 total Here is a open time. This should be checked if DOC was opened properly. So far, worst was fix in 5.2 of not opening in 5.1.
Slowdown in 40 was in 43all commit f14ed43d8e6708b63145fb63cfc109c223d9e344: from 83,86s user 1,97s system 96% cpu 1:28,85 total to 125,91s user 1,98s system 97% cpu 2:11,14 total Range: https://cgit.freedesktop.org/libreoffice/core/log/?qt=range&q=9ed34f8137e1ec4f58151eba74507102192cb8fd..a20f9a410fdd3f776f870434bc39219d5fc64b40
Big slowdown in 5.2 repo in commit 68fd35405fcaa694e09e988cef4847772ef8406d: from 5.2o 68,83s user 2,07s system 94% cpu 1:15,35 total to 5.2m 244,74s user 2,97s system 98% cpu 4:11,05 total author Justin Luth <justin_luth@sil.org> 2015-11-27 commit 0d127baed75929e744d5b6249f510012cfbc0e88 tdf#91083 - .doc: emulate table keep-with-next paragraph Adding Justin for comment.
Another slowdown in 6.4 repo in commit 3c8644c50f63c207b563ccd14f62efb8e10c531a: from 311,57s user 1,72s system 92% cpu 5:39,61 total to 0,11s user 0,08s system 0% cpu 8:56,65 total (those times are for 2nd run, 1st run is worse and awfully slow: to 1017,93s user 1,49s system 99% cpu 17:03,84 total) author László Németh <nemeth@numbertext.org> 2019-07-05 commit b86b87eb34c686c67ae86c6f635e5218a5654898 tdf#120338 DOCX: reject other paragraph formatting changes
Some improvement in 7.4 repo: from 760,33s user 1,48s system 99% cpu 12:44,19 total to 411,96s user 1,27s system 99% cpu 6:55,83 total commit 86039563de87149a01ffb980b5ec99074b98fd5e author Luboš Luňák <l.lunak@collabora.com> May 14 2022 std::stable_sort() where libc++ debug mode breaks a unittest Adding Luboš here to see this unexpected? improvement for opening DOC.
This problem still exists in v7.5 RC1: Version: 7.5.0.1 (X86_64) / LibreOffice Community Build ID: 77cd3d7ad4445740a0c6cf977992dafd8ebad8df CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Vulkan; VCL: win Locale: en-GB (en_GB); UI: en-GB Calc: CL threaded
This problem still exists in v24.2.0.0 Alpha 1 x64: Version: 24.2.0.0.alpha1 (X86_64) / LibreOffice Community Build ID: 06946980c858649160c634007e5fac9a5aa81f38 CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: en-GB (en_GB); UI: en-GB Calc: threaded