Also, for the ones having crashes at startup
@AlGrenadine - My apologies if I'm hijacking the thread. I do iOS development for a living and I'm having crashes at startup. Thought it might help you to investigate crashes if you had some more data points. My gut feel is that the crashes are related to networking code. I haven't been extremely scientific, but I did try a bunch of things to see if my assumption might possibly have some merit. Feel free to PM if there's any additional data I can provide. I don't post much, but I'm on the forum MANY times a day.
TL;DR - If you're having crashes, and they are not related to MacOS incompatibility, try turning off Wifi.
Testing details below:
Environment:
Fractool 2.39
MacOS 10.11.5
Current networking environment: Connecting via WiFi, but I must enable VPN in order to make connections with the outside world.
Caveat: I see similar behavior when connecting from home where I don't require VPN.
Test 1:
Computer has been running a while. Wifi enabled. VPN connected.
Start Fractool - crash.
Crash report indicates a crash on the main thread as part of some networking code. (Rest of the crash report omitted)
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 org.qt-project.QtNetwork 0x00000001056c8425 0x105629000 + 652325
1 com.apple.CFNetwork 0x00007fff984a9a00 executionContextPerform(void*) + 1191
2 com.apple.CoreFoundation 0x00007fff9b74b881 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17
3 com.apple.CoreFoundation 0x00007fff9b72afbc __CFRunLoopDoSources0 + 556
4 com.apple.CoreFoundation 0x00007fff9b72a4df __CFRunLoopRun + 927
5 com.apple.CoreFoundation 0x00007fff9b729ed8 CFRunLoopRunSpecific + 296
6 org.qt-project.QtNetwork 0x00000001056c7835 0x105629000 + 649269
7 org.qt-project.QtNetwork 0x00000001056c8681 QNetworkProxyFactory::systemProxyForQuery(QNetworkProxyQuery const&) + 17
Test 2:
Restart the computer. (So Wifi enabled, but VPN not connected upon restart)
As soon as humanly possible after startup, start Fractool.
IT WORKED.
Immediately close Fractool.
Immediately restart Fractool.
IT WORKED
Close
Restart....crash. Same type of crash log.
Test 3:
Restart the computer. (So Wifi enabled, but VPN not connected upon restart)
As soon as humanly possible after startup, start Fractool
IT WORKED
Started looking around in Fractool - was kinda slow poking around
Clicked the AxeChange tab
CRASH
Hmm...
Test 4:
Turn Wifi OFF
Restart the computer
As soon as humanly possible after startup, start Fractool
IT WORKED
Could not reproduce crash despite starting/stopping several times.
Could not reproduce crash despite clicking on all tabs.
Test 5:
Building upon previous test, turn Wifi ON
Tried starting Fractool
CRASH
Last test:
Turn Wifi ON
Restart computer
I connected to VPN
I ensured I could browse web pages.
start Fractool
CRASH
Turn off Wifi
start Fractool
WORKED
My assumption is that starting Fractool "as soon as humanly possible" after startup may be enabling Fractool to launch before the network gets enabled. No *proof* of that, but it seems plausible. That at least fits with my limited tests of running it with Wifi OFF. Once a network connection is available (Wifi is ON. VPN is irrelevant), I get crashes in the main thread with references to QNetworkProxyFactory::systemProxyForQuery.