Bug 127261 - Very slow verifying upon first run (macOS)
Summary: Very slow verifying upon first run (macOS)
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Installation (show other bugs)
Version:
(earliest affected)
5.0 all versions
Hardware: All macOS (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: MacOS-Performance
  Show dependency treegraph
 
Reported: 2019-09-01 10:21 UTC by laurens
Modified: 2023-03-18 21:40 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description laurens 2019-09-01 10:21:54 UTC
I've had this problem since LO 5.x across multiple Macs:

Version: 6.3.0.4
Build ID: 057fc023c990d676a43019934386b85b21a9ee99
CPU threads: 12; OS: Mac OS X 10.14.6; UI render: default; VCL: osx; 
Locale: nb-NO (en_NO.UTF-8); UI-Language: en-US


2018 MBP lots of CPU and RAM
diskimages-helper  is 100% for 5+ minutes trying to verify LibreOffice.app when I perform an installation

This gives a poor first impression for users and is very inconvenient if I want to try out new versions to see if bugs have been fixed.

I know that I can (temporarily) disable Gatekeeper or other workarounds, but this is not recommended.

I have tried searching the bugzilla bug reports, but have not found any duplicates.
Comment 1 Alex Thurgood 2019-09-04 05:14:47 UTC
Confirming. It has indeed been this way for a very long time...
Comment 2 Alex Thurgood 2019-09-04 05:18:36 UTC
It is even longer if the xattr quarantine property has been set by Gatekeeper, see for example bug 97530.
Comment 3 QA Administrators 2021-09-04 04:01:45 UTC Comment hidden (obsolete)
Comment 4 Roman Kuznetsov 2021-09-05 10:05:47 UTC
I'm not sure it's an our bug. I think modern macOS checks all third-party software. And it takes many time just because LibreOffice too big
Comment 5 eisa01 2023-03-18 21:40:47 UTC
I don't have this behavior any more

I think it improved after the compression of the disk image was changed?