Created attachment 56036 [details] example WMF picture Problem description: When you drag & drop attached WMF picture into Writer/Impress or Draw then it can take up to 40 seconds of 100% CPU load before the picture is shown. When the document is saved and re-opened the time it takes to open it directly proportional to the number of WMF pictures used: ie with 5 example WMF pictures it will take 5 time as long (with 100% cpu load) as with one picture. Steps to reproduce: 1. open new drawing or Text document or Presentation 2. drag & drop example WMF file into document 3. Watch high CPU load for long time with Task Manager. Current behavior: Adding WMF picture to document or opening document with WMF picture in it takes a very long time. LibreOffice appears to be locked up for that duration. Expected behavior: Expect to show the WMF picture immediately. Powerpoint shows presentation with multiple WMF pictures in it within seconds. Platform (if different from the browser): Browser: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:9.0.1) Gecko/20100101 Firefox/9.0.1
Reproduced with LOdev 3.5.0rc1 e40af8c-10029e3-615e522-88673a2-727f724 Ubuntu 10.04.3 x86 Linux 2.6.32-37-generic Russian UI
I can confirm this bug on platform Version 4.0.0.0.beta1 (Build ID: 87906242e87d3ddb2ba9827818f2d1416d80cc7)
Created attachment 71683 [details] Word document containing another WMF which makes LibO hang .doc 97-2003
I can confirm this bug on LibreOffice 4.0.0.0 beta1 and with this another WMF picture. Note that Apache OpenOffice 3.4 and OOO 3.3 can open these files normally, albeit some graphicals errors.
I can confirm this bug on platform LO 4 RC1, Version 4.0.0.1 (Build ID: 527dba6f6e0cfbbc71bd6e7b88a52699bb48799) See also bug 45820, is this a similar issue?
This bug is still present on LibreOffice Version: 4.1.0.4 Build ID: 89ea49ddacd9aa532507cbf852f2bb22b1ace28. It takes about 40 seconds to open the attached example WMF file. Note that Apache OpenOffice 4.0 opens this WMF file normally within a reasonable time, about 1 second.
** 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 (4.4.1 or later) 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 your help! -- The LibreOffice QA Team This NEW Message was generated on: 2015-04-18
Present in LibreOffice 4.4.3.2
Callgrind analysis showed that it is the same as bug 45820. *** This bug has been marked as a duplicate of bug 45820 ***