Changes between Version 4 and Version 5 of Ticket #9388, comment 13


Ignore:
Timestamp:
Jul 18, 2023, 11:14:44 PM (2 years ago)
Author:
Tom Goddard

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #9388, comment 13

    v4 v5  
    2121I tried using QTWEBENGINE_CHROMIUM_FLAGS as described here https://doc.qt.io/qt-6/qtwebengine-debugging.html to get more logging info but did not get anything on stderr, nor did using qInstallMessageHandler() help get any logging.
    2222
    23 But I noticed in the console log just before QtWebEngineProcess crashes the following "CODE SIGNING: 87195[QtWebEngineProce] vm_map_protect:6059(0x0,0x0,0x7) can't have both write and exec at the same time" and searching for that led me to https://forum.qt.io/topic/102212/qtwebengine-signing-issues/3 which is old from 2019 but said that entitlement "com.apple.security.cs.disable-executable-page-protection" was needed to avoid QtWebEngineProcess crashes.  Maybe our ChimeraX entitlement "com.apple.security.cs.allow-unsigned-executable-memory" is causing the issue.
     23But I noticed in the console log just before QtWebEngineProcess crashes the following
     24
     25{{{
     26CODE SIGNING: 87195[QtWebEngineProce] vm_map_protect:6059(0x0,0x0,0x7) can't have both write and exec at the same time
     27}}}
     28
     29and searching for that led me to https://forum.qt.io/topic/102212/qtwebengine-signing-issues/3 which is old from 2019 but said that entitlement "com.apple.security.cs.disable-executable-page-protection" was needed to avoid QtWebEngineProcess crashes.  Maybe our ChimeraX entitlement "com.apple.security.cs.allow-unsigned-executable-memory" is causing the issue.
    2430
    2531This page describes the Apple entitlements related to executable memory: https://developer.apple.com/documentation/security/hardened_runtime