diff options
| author | Tor Arne Vestbø <tor.arne.vestbo@qt.io> | 2023-03-28 14:48:06 +0200 |
|---|---|---|
| committer | Tor Arne Vestbø <tor.arne.vestbo@qt.io> | 2023-03-31 23:01:51 +0200 |
| commit | e81aa64280e9835121769085023034e919274745 (patch) | |
| tree | ae10b9317f51cc76f2f6c700cbb39721eb195968 /src/corelib/io/qsettings_win.cpp | |
| parent | 3236b64db8bb26a6c1c2c288cb47ecc08a7d526f (diff) | |
macOS: Move application sandbox checking to secondary thread
We use the macOS Security framework to check whether the application is
sandboxed or not, in which case we might have to limit or change some of
the functionality of Qt, such as which shared memory backend to use.
Calls to SecStaticCodeCheckValidityWithErrors should ideally not be done
on the main thread, as the function may not return immediately, and we
get runtime analysis warnings about this in Xcode:
This method should not be called on the main thread as it may lead to
UI unresponsiveness.
To improve the situation we spin up a short lived thread at library
load that resolves the sandboxing state, ready to be queried when
needed from Qt.
Pick-to: 6.5
Change-Id: I52cdc1bf6aef05c3b93b43f67b3fb46035996b3a
Reviewed-by: Thiago Macieira <thiago.macieira@intel.com>
Reviewed-by: Mårten Nordheim <marten.nordheim@qt.io>
Diffstat (limited to 'src/corelib/io/qsettings_win.cpp')
0 files changed, 0 insertions, 0 deletions