Description: When i open .dotm file with a standard "Blue spheres resume" MS template and then try to save file as docx or docm Writer is hanging. Steps to Reproduce: 1.Open dotm file with a standard "Blue spheres resume" MS template (file attached) 2.Save as docx or docm 3. Actual Results: Writer is hanging (crashed) Expected Results: save the file Reproducible: Always User Profile Reset: Yes OpenGL enabled: Yes Additional Info: Version: 7.1.6.2 (x64) / LibreOffice Community Build ID: 0e133318fcee89abacd6a7d077e292f1145735c3 CPU threads: 8; OS: Windows 10.0 Build 19041; UI render: Skia/Raster; VCL: win Locale: uk-UA (uk_UA); UI: uk-UA Calc: CL
Created attachment 176333 [details] file include standard "Blue spheres resume" MS template
it doesn't crash nor hang for me in Version: 7.3.0.0.alpha1+ / LibreOffice Community Build ID: 4180b2f7855479f9187cd259d57c06e9fedfb802 CPU threads: 4; OS: Linux 5.10; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded it just takes 2 minutes 20 seconds to save. @Andrew, in your case, does it save the document if you wait a bit longer ?
(In reply to Xisco Faulí from comment #2) > it doesn't crash nor hang for me in > > Version: 7.3.0.0.alpha1+ / LibreOffice Community > Build ID: 4180b2f7855479f9187cd259d57c06e9fedfb802 > CPU threads: 4; OS: Linux 5.10; UI render: default; VCL: gtk3 > Locale: en-US (en_US.UTF-8); UI: en-US > Calc: threaded > > it just takes 2 minutes 20 seconds to save. > > @Andrew, in your case, does it save the document if you wait a bit longer ? Hi @Xisco Faulí ! You're right. After 10 minutes 20 seconds of waiting with the window hanging, the document was saved. Below is a screenshot of the window while waiting https://i.imgur.com/LcnFXM0.png
thanks for your feedback. Let's turn this into a performance issue
Created attachment 176347 [details] Flamegraph On pc Debian x86-64 with master sources updated today + gen rendering, I just did this: - open dot file - save as docx was it the right thing to do? Indeed, I didn't wait long to have the docx (of course, it's a Ryzen 5 2600 + 32GB but there are far more powerful machines now).
Forget what I said in my last comment about the time, I checked with a chrono, it took 1min25 so very long for a one page doc.
Instantly saving in Version: 7.4.0.0.alpha1+ (x64) / LibreOffice Community Build ID: b6266207b55a7633dc82b02142215757512adfb7 CPU threads: 8; OS: Windows 10.0 Build 19043; UI render: Skia/Vulkan; VCL: win Locale: ru-RU (ru_RU); UI: en-US Calc: threaded Andrew, please retest in latest 7.4 dev build https://dev-builds.libreoffice.org/daily/master/current.html
Dear Andrew, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping
Dear Andrew, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp