Description: The PDF export of the attached presentation is slow in recent LibO versions Steps to Reproduce: 1. Open attachment 133491 [details] (bug 108037) (based on bug 104479#c26) 2. Export it to PDF with default settings (300 dpi 90%) Actual Results: Export takes around 60 sec Expected Results: Export should take around 30 seconds Reproducible: Always User Profile Reset: No Additional Info: Crashing in Version: 5.5.0.0.alpha0+ Build ID: d57e6cd9dcc96112994ca2b14ac45896e86b26e5 CPU threads: 4; OS: Windows 6.19; UI render: default; TinderBox: Win-x86@42, Branch:master, Time: 2017-05-18_22:43:07 Locale: nl-NL (nl_NL); Calc: CL but found in Version: 5.2.5.0.0+ Build ID: a4d4fbeb623013f6377b30711ceedb38ea4b49f8 CPU Threads: 4; OS Version: Windows 6.2; UI Render: GL; TinderBox: Win-x86@62-merge-TDF, Branch:libreoffice-5-2, Time: 2016-12-24_14:43:55 Locale: nl-NL (nl_NL); Calc: CL and in Version: 5.0.0.5 Build ID: 1b1a90865e348b492231e1c451437d7a15bb262b Locale: nl-NL (nl_NL) but not in Version: 4.3.7.2 Build ID: 8a35821d8636a03b8bf4e15b48f59794652c68ba User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:45.0) Gecko/20100101 Firefox/45.0
Could be related to or a dupe of bug 106587 (but not quite sure)
Yep, 46 secs with 5.5, 26 secs with 3.6. Should probably do a callgrind later. The bisected commit in bug 106587 is from August 2013, while 4.3.0 was released August 2014, so I guess it is different https://wiki.documentfoundation.org/ReleasePlan/4.3 Arch Linux 64-bit, KDE Plasma 5 Version: 5.5.0.0.alpha0+ Build ID: c855400e9686ddd8bcba5691393f839f6f52c966 CPU threads: 8; OS: Linux 4.11; UI render: default; VCL: kde4; Locale: fi-FI (fi_FI.UTF-8); Calc: group Built on June 2nd 2017 Arch Linux 64-bit Version 3.6.7.2 (Build ID: e183d5b)
Created attachment 133834 [details] Callgrind output from 5.5 Arch Linux 64-bit, KDE Plasma 5 Version: 5.5.0.0.alpha0+ Build ID: c855400e9686ddd8bcba5691393f839f6f52c966 CPU threads: 8; OS: Linux 4.11; UI render: default; VCL: kde4; Locale: fi-FI (fi_FI.UTF-8); Calc: group Built on June 2nd 2017
Apparently the same as 106587, see Armin's comment: https://bugs.documentfoundation.org/show_bug.cgi?id=106587#c16 WONTFIX because: "as long as PDF export is based on Metafile and not on primitives that info is just not transportable in Metafiles and thus cannot be used in PDF exports. Only thing doable now would be to 'play' with the fMaximumArea limitation on the cost of getting bad edges again in PDF exports (and reports for that)." *** This bug has been marked as a duplicate of bug 106587 ***