Description: Scaling a simple SVG is quite CPU intensive compared to Word Steps to Reproduce: 1.Open attached file 2.Resize the grouped SVG image by clicking at a corner and resize 3.Monitor CPU usage or (a bit less intense) 1. Open Writer 2. Add a shape (smiley) 3. Resize the shape Actual Results: CPU consumption between 18-23% Expected Results: Around 5% like MS Word Reproducible: Always User Profile Reset: No Additional Info: Found in: Version: 5.4.0.0.alpha0+ Build ID: d0288a482a3dc0f50f535565e4c66a95bb140942 CPU Threads: 4; OS Version: Windows 6.19; UI Render: default; TinderBox: Win-x86@42, Branch:master, Time: 2016-12-26_23:25:18 Locale: nl-NL (nl_NL); Calc: CL and in LibreOffice 3.3.0 OOO330m19 (Build:6) tag libreoffice-3.3.0.4 User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:45.0) Gecko/20100101 Firefox/45.0
Created attachment 129988 [details] Example file
While scaling back and forth, one of my CPUs goes even over 60%, hovering at 40-50%. Essentially the same in 3.3 Arch Linux 64-bit, KDE Plasma 5 Version: 5.4.0.0.alpha0+ Build ID: 6c2b8cb5b136b63b3ea295528b845d37b5dd9000 CPU Threads: 8; OS Version: Linux 4.8; UI Render: default; VCL: kde4; Locale: fi-FI (fi_FI.UTF-8); Calc: group Built on December 28th 2016 Arch Linux 64-bit LibreOffice 3.3.0 OOO330m19 (Build:6) tag libreoffice-3.3.0.4
The attached file does not contain any SVG image. Resizing the drawing object works quickly, without any unnormal CPU work increasing. Opening the attached file in Word 2010 and resizing there, uses the same processing power as LibreOffice. I use Version: 5.4.0.0.alpha0+ Build ID: 690cf2a5ac87d3d05c45a86944e7f6b0adf12cf2 CPU Threads: 4; OS Version: Windows 6.1; UI Render: default; TinderBox: Win-x86@62-merge-TDF, Branch:MASTER, Time: 2016-12-15_18:59:20 Locale: de-DE (de_DE); Calc: group Which version of Word can handle SVG images?
@Regina Henschel I should say drawing objects, instead of svg. Resizing is a drawing object does work smooth. But CPU work is quite intense, while scaling back and forth.
The issue is similar to bug 105016. So closing this one as NAB.