Sample file: https://bugs.documentfoundation.org/attachment.cgi?id=133113 Version: 6.2.1.2 Build ID: libreoffice-6.2.1.2-snap1 CPU threads: 8; OS: Linux 4.15; UI render: default; VCL: gtk3; Locale: en-US (en_US.UTF-8); UI-Language: en-US Calc: threaded Time from clicking "Open" to seeing the "Macros" warning dialog: 17 seconds Version: 6.2.0.1 Build ID: 0412ee99e862f384c1106d0841a950c4cfaa9df1 CPU threads: 8; OS: Linux 4.15; UI render: default; VCL: gtk3; Locale: en-US (en_US.UTF-8); UI-Language: en-US Calc: threaded Time from clicking "Open" to seeing the "Macros" warning dialog: 3.5 seconds Is this a SNAP issue, or a regression? Config: Thinkpad X1 Carbon laptop with SSD and 16GB RAM, Core i5 CPU. Files were loaded "warm", i.e. measured the load time for the second load. Does LibreCalc have tests for respecting a "performance budget"[1], for example ensuring that a given file loads on a given or better configuration in at most X seconds? [1]: the "performance budget" concept for web apps - https://addyosmani.com/blog/performance-budgets/
No delay here with Version: 6.2.2.2 (x64) Build ID: 2b840030fec2aae0fd2658d8d4f9548af4e3518d CPU threads: 4; OS: Windows 10.0; UI render: GL; VCL: win; Locale: es-ES (es_ES); UI-Language: en-US Calc: threaded Maybe some option gives the issue, please test with a clean profile Menu/Help/Restart in Safe mode
I can not see the delay in 6.2.3.2 DEB. Maybe it was a problem with the SNAP package specifically?
You could report it here in case it persists in 6.3: https://bugs.launchpad.net/ubuntu/+source/libreoffice
I understand that slow loading *of LibreCalc* from the snap should be reported to the Ubuntu packagers, but the issue I ran into was slow loading of files AFTER Calc had been started.
(In reply to Dan Dascalescu from comment #4) > I understand that slow loading *of LibreCalc* from the snap should be > reported to the Ubuntu packagers, but the issue I ran into was slow loading > of files AFTER Calc had been started. If Canonical devs determine the problem to be in upstream, we can always revisit this report.