<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Segmentation fault since macOS 11 Update in Qt Maps SDK Questions</title>
    <link>https://community.esri.com/t5/qt-maps-sdk-questions/segmentation-fault-since-macos-11-update/m-p/1004684#M3845</link>
    <description>&lt;P&gt;As Big Sur was just released a few weeks ago, our previous releases have not been tested and do not list Big Sur as a supported platform. Historically, most upgrades "just worked" regardless of an official support statement from us, so it is unclear at this point if Big Sur is any different or not.&lt;/P&gt;&lt;P&gt;Here is the 100.6 system requirements -&amp;nbsp;&lt;A href="https://developers.arcgis.com/qt/latest/qml/guide/system-requirements-100-6.htm" target="_blank"&gt;https://developers.arcgis.com/qt/latest/qml/guide/system-requirements-100-6.htm&lt;/A&gt;&amp;nbsp;--&amp;nbsp;High Sierra and Mojave are the 2 supported versions of macOS.&lt;/P&gt;&lt;P&gt;We are currently working on finishing up our 100.10 release, and we intend to fully test and support Big Sur for that release.&lt;/P&gt;</description>
    <pubDate>Wed, 25 Nov 2020 15:47:00 GMT</pubDate>
    <dc:creator>LucasDanzinger</dc:creator>
    <dc:date>2020-11-25T15:47:00Z</dc:date>
    <item>
      <title>Segmentation fault since macOS 11 Update</title>
      <link>https://community.esri.com/t5/qt-maps-sdk-questions/segmentation-fault-since-macos-11-update/m-p/1003952#M3840</link>
      <description>&lt;P&gt;Hallo,&lt;/P&gt;&lt;P&gt;i'm using the Arcgis QML SDK 100.6 on MacOS with Qt 5.13.1.&lt;/P&gt;&lt;P&gt;Since i've updated to MacOS Big Sur (11.0.1) my Application starts up, the window where the map should be stays grey and the application terminates with a Segmentation Fault as soon as i click the window with the map.&lt;/P&gt;&lt;P&gt;Here is the Failure Report from macOS:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;Process:               Curves [11345]
Path:                  /Users/USER/*/Curves.app/Contents/MacOS/Curves
Identifier:            fg.Curves
Version:               0
Code Type:             X86-64 (Native)
Parent Process:        Qt Creator [657]
Responsible:           Qt Creator [657]
User ID:               501

Date/Time:             2020-11-23 15:17:00.276 +0100
OS Version:            macOS 11.0.1 (20B50)
Report Version:        12
Bridge OS Version:     3.0 (14Y908)
Anonymous UUID:        93B5BB12-6E01-DC36-648F-EB4AD9B043C0


Time Awake Since Boot: 10000 seconds

System Integrity Protection: enabled

Crashed Thread:        0  Dispatch queue: com.apple.main-thread

Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:       KERN_INVALID_ADDRESS at 0x0000000000000008
Exception Note:        EXC_CORPSE_NOTIFY

Termination Signal:    Segmentation fault: 11
Termination Reason:    Namespace SIGNAL, Code 0xb
Terminating Process:   exc handler [11345]

VM Regions Near 0x8:
--&amp;gt; 
    __TEXT                      102d2b000-102e97000    [ 1456K] r-x/r-x SM=COW  /Users/*/Curves.app/Contents/MacOS/Curves

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   org.qt-project.QtGui          	0x00000001053a43f4 QTextDocument::firstBlock() const + 4
1   libEsriCommonQt.dylib         	0x00000001038b0607 QRTImpl::InteractionHandler::openAttributionHyperlink(QMouseEvent const&amp;amp;) + 439
2   libEsriCommonQt.dylib         	0x00000001038b03d0 QtPrivate::QFunctorSlotObject&amp;lt;QRTImpl::InteractionHandler::connectTimers()::$_1, 0, QtPrivate::List&amp;lt;&amp;gt;, void&amp;gt;::impl(int, QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) + 336
3   org.qt-project.QtCore         	0x000000010600de4b QMetaObject::activate(QObject*, int, int, void**) + 1435
4   org.qt-project.QtCore         	0x0000000106015d52 QTimer::timerEvent(QTimerEvent*) + 98
5   org.qt-project.QtCore         	0x0000000106006916 QObject::event(QEvent*) + 102
6   org.qt-project.QtWidgets      	0x0000000104c199fd QApplicationPrivate::notify_helper(QObject*, QEvent*) + 269
7   org.qt-project.QtWidgets      	0x0000000104c1ae02 QApplication::notify(QObject*, QEvent*) + 594
8   org.qt-project.QtCore         	0x0000000105fdccc4 QCoreApplication::notifyInternal2(QObject*, QEvent*) + 212
9   org.qt-project.QtCore         	0x000000010603639f QTimerInfoList::activateTimers() + 991
10  libqcocoa.dylib               	0x0000000106653742 QCocoaEventDispatcherPrivate::activateTimersSourceCallback(void*) + 18
11  com.apple.CoreFoundation      	0x00007fff204339fc __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17
12  com.apple.CoreFoundation      	0x00007fff20433964 __CFRunLoopDoSource0 + 180
13  com.apple.CoreFoundation      	0x00007fff204336df __CFRunLoopDoSources0 + 248
14  com.apple.CoreFoundation      	0x00007fff20432111 __CFRunLoopRun + 890
15  com.apple.CoreFoundation      	0x00007fff204316be CFRunLoopRunSpecific + 563
16  com.apple.HIToolbox           	0x00007fff2869dfd0 RunCurrentEventLoopInMode + 292
17  com.apple.HIToolbox           	0x00007fff2869ddcc ReceiveNextEventCommon + 709
18  com.apple.HIToolbox           	0x00007fff2869daef _BlockUntilNextEventMatchingListInModeWithFilter + 64
19  com.apple.AppKit              	0x00007fff22c4af85 _DPSNextEvent + 883
20  com.apple.AppKit              	0x00007fff22c4974b -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1366
21  com.apple.AppKit              	0x00007fff22c3bbda -[NSApplication run] + 586
22  libqcocoa.dylib               	0x00000001066544f3 QCocoaEventDispatcher::processEvents(QFlags&amp;lt;QEventLoop::ProcessEventsFlag&amp;gt;) + 2579
23  org.qt-project.QtCore         	0x0000000105fd813f QEventLoop::exec(QFlags&amp;lt;QEventLoop::ProcessEventsFlag&amp;gt;) + 431
24  org.qt-project.QtCore         	0x0000000105fdd2d2 QCoreApplication::exec() + 130
25  fg.Curves                     	0x0000000102d3385d main + 1565 (main.cpp:73)
26  libdyld.dylib                 	0x00007fff20356631 start + 1&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is there a fix for this? I've reinstalled the SKD. I would prefer not to update, because then i would have to update Qt as well, which would be quite the undertaking.&lt;/P&gt;&lt;P&gt;Thanks for your help!&lt;/P&gt;</description>
      <pubDate>Mon, 23 Nov 2020 14:18:09 GMT</pubDate>
      <guid>https://community.esri.com/t5/qt-maps-sdk-questions/segmentation-fault-since-macos-11-update/m-p/1003952#M3840</guid>
      <dc:creator>FlorianGschwandtner</dc:creator>
      <dc:date>2020-11-23T14:18:09Z</dc:date>
    </item>
    <item>
      <title>Re: Segmentation fault since macOS 11 Update</title>
      <link>https://community.esri.com/t5/qt-maps-sdk-questions/segmentation-fault-since-macos-11-update/m-p/1004684#M3845</link>
      <description>&lt;P&gt;As Big Sur was just released a few weeks ago, our previous releases have not been tested and do not list Big Sur as a supported platform. Historically, most upgrades "just worked" regardless of an official support statement from us, so it is unclear at this point if Big Sur is any different or not.&lt;/P&gt;&lt;P&gt;Here is the 100.6 system requirements -&amp;nbsp;&lt;A href="https://developers.arcgis.com/qt/latest/qml/guide/system-requirements-100-6.htm" target="_blank"&gt;https://developers.arcgis.com/qt/latest/qml/guide/system-requirements-100-6.htm&lt;/A&gt;&amp;nbsp;--&amp;nbsp;High Sierra and Mojave are the 2 supported versions of macOS.&lt;/P&gt;&lt;P&gt;We are currently working on finishing up our 100.10 release, and we intend to fully test and support Big Sur for that release.&lt;/P&gt;</description>
      <pubDate>Wed, 25 Nov 2020 15:47:00 GMT</pubDate>
      <guid>https://community.esri.com/t5/qt-maps-sdk-questions/segmentation-fault-since-macos-11-update/m-p/1004684#M3845</guid>
      <dc:creator>LucasDanzinger</dc:creator>
      <dc:date>2020-11-25T15:47:00Z</dc:date>
    </item>
    <item>
      <title>Re: Segmentation fault since macOS 11 Update</title>
      <link>https://community.esri.com/t5/qt-maps-sdk-questions/segmentation-fault-since-macos-11-update/m-p/1006576#M3861</link>
      <description>&lt;P&gt;I have now found out that this is a problem with Qt 5.13: I can't get the samples to run with 5.13 and 100.6.&lt;/P&gt;&lt;P&gt;The only remedy i found is to update to Qt 5.15.2. The Arcgis Version does not matter.&lt;/P&gt;</description>
      <pubDate>Thu, 03 Dec 2020 11:53:21 GMT</pubDate>
      <guid>https://community.esri.com/t5/qt-maps-sdk-questions/segmentation-fault-since-macos-11-update/m-p/1006576#M3861</guid>
      <dc:creator>FlorianGschwandtner</dc:creator>
      <dc:date>2020-12-03T11:53:21Z</dc:date>
    </item>
  </channel>
</rss>

