Clementine Mac Os Mojave

The oldest MacBook Pro which can upgrade to Mojave shipped with 10.7, Lion. The oldest MacBook had Mac OS X 10.10 installed. The oldest Mac Pro on the list above with the compatible graphics cards, had 10.6 originally installed, and is the only Mac that shipped with 10.6 that can install Mojave. The problem with 64-bit architecture is that many developers choose not to optimize their 32-bit applications for Mac with the release of Catalina. If that’s the case and you can’t find an alternative for the missing app, you might need to downgrade back to Mojave. Luckily, there’s a way to fix most problems with apps not working in Catalina.

Mac Os Mojave Requirements
Clementine Mac Os Mojave Dmg
Mojave Os Download
Mac Os Mojave 10.14
Mojave Os Download Mac
Clementine Mac Os Mojave 10.10
Clementine Macos Mojave

The Mac Silver Tower 4,1 and 5,1 remain one of the most powerful Macs ever made, depending on your processor. Even the eight core 2.26 GHz version is incredibly powerful and fast, outrunning any MacBook Pro and most iMacs, as will a hexacore 3.33 GHz or 3.46 GHz. Certainly they are more expandable, repairable and upgradeable than any other Mac built since, with SATA SSD and PCI cards and graphic card upgrades readily available and easily installed. For video editors, the Mac Pro Silver Tower is one of the best computers ever built.

In terms of cost for performance, no current Mac whether iMac or iMac Pro can touch the 4,1 and 5,1 Silver Towers. What's especially wonderful is that both of them will still run the latest Apple OS and software perfectly, with just a bit of preparation. I'll take you through the steps of a successful deployment of a 4,1 Silver Tower with High Sierra.

Start by Testing Your Hardware: Apple Hardware Test

The first thing you should do is test your hardware. This is easier said than done on older hardware. Apple has some lovely software called Apple Hardware Test a.k.a. as AHT. There's no joy in suffering through crashes which are hardware related, trying to debug your OS (software).

Normally you find AHT at this path /System/Library/CoreServices/.diagnostics

Unfortunately, recent versions of the OS have not included AHT or at least not for older computers. Happily some enterprising Apple fans have collected all the versions of AHT out there for all kinds of Apple computers including Powermac, Powerbook, iBook, iMac, MacMini, MacPro, MacBook and MacBooks Pro.

As we have mainly MacPros here from 4,1 generation, mostly upgraded to 5,1 firmware, we generally prefer the bundle which includes both 4,1 and 5,1 MacPros.

Installing AHT should be as easy as just as just copying the .diagnostics hidden folder over. Through OS X 10.10 that was all a user had to do to install a working AHT and then press D when restarting his or her Mac.

But since OS X 10.11 El Capitan, it's not that easy. To be able to install any files at all to the System folder, first you must disable System Integrity Protection. Apple and third party sites will try to scare you off of turning off SIP. Apple OS X users got by for fifteen years without SIP so it's not as big a deal as it sounds. Any malware clever enough to deploy on OS X will find a way to do so even with SIP turned on. SIP is just putting another lock on the door. Locks rarely stopped an expert burglar (he'll just go through a window).

Disabling SIP

Fortunately turning off SIP is easier than it looks. If you have a solid OS X 10.11, 10.12 or 10.13 installation you will have a recovery partition which can be accessed as simply as pressing command-R while rebooting before the grey boot screen comes up. This will take you to the recovery desktop which gives you access to a fully rooted Terminal app.

Inside Terminal, you can check SIP status by typing csrutil status. If you see System Integrity Protection status: enabled. just type csrutil disable. Terminal will print a message which says Reboot to disable System Integrity Protection. Isn't it great when command line commands say what they do and do what they say?

Graphic Card Limitations: Install a native Mac card for AHT and firmware updates

Since about 10.8.3, Apple OS X will allow you to install almost any AMD video card (i.e. Radeon 5770, 5870, 6850, 6870, 7850, 7870) and with Nvidia drivers you can use most modern Nvidia graphic cards (including the very popular GTX 7xx and 9xx series). These third party cards do not show the Mac boot screen however. You can probably turn SIP off without a boot screen card but you will not be able to use AHT without a native Mac graphic card. Make sure you have an Apple flashed AMD 5770 or 5870 or an Nvidia 120 handy before you proceed or you won't get far (there's a couple of firmware updates ahead). Even an old Apple Radeon 4870 will get the job done.

When you are finished the full install to High Sierra, you can put your high powered Windows graphic card back in your Mac Pro. With High Sierra, you have access to the AMD RX580 and RX Vega 56 with no system hacks on the red side.

For video editors: Nvidia's GTX 1070 and 1080 are equally available to you. For FCPX, AMD's RX580 is the much better choice. For Adobe CS and CC suites, Nvidia is slightly better. For Davinci Resolve 15 and up, both Nvidia (CUDA) and AMD (OpenCL engine) are good - the more powerful the card the better.

Making Hidden Files Visible to Finish the AHT Install

Now you should reboot normally with no modifier keys pressed. When you reach the desktop (probably after logging in), you should now either install a demo of Forklift (gives you a twin pane interface like the old Norton Commander on DOS and a GUI switch to hidden files) or make hidden files visible. This is an easy trip to the terminal. Type: defaults write com.apple.finder AppleShowAllFiles YES. After that you should press command-option-ESC and choose 'Finder'. You'll see a button to 'Restart'. When Finder restarts, hidden files will be visible.

Apparently in OS X Sierra (10.12) and later, Apple has exceptionally made life easier for power users by enabling this command: command-shift-. This does not work on El Capitan 10.11 (just tested).

At this point you can navigate down to the .diagnostics folder on your 022-5348-A.dmg disk image and copy it over to /System/Library/CoreServices/.diagnostics on your boot drive.

You are now ready to use Apple Hardware Test. Just restart one more time while holding down D on an Apple keyboard.

Keep in mind AHT does not work on Hackintoshes of any breed. AHT is just for testing Apple computers. In testing a half a dozen silver towers, I've found that sensor errors are most common. Depending on the sensor your silver tower will run just fine despite the invisible error.

On the other hand, video card sensor errors on the other hand will require you to run headless (quickly enable VNC and/or screen sharing in the 'Sharing' control panel while you have access to a shaky image. If you have no image, you could move that startup disk over to another mac and enable sharing on before rebooting with that startup disk on the troubled Mac. A headless silver tower makes a great remote file server to access from another Mac. If you have Gigabit ethernet (most wired routers these days are Gigabit capable), you'll be able to transfer files at up to 100 MB/sec which is faster than most spinning disks.

Installing the 5,1 Firmware Update

If you have a Mac Pro 5,1, you don't have to install a firmware update to be able to install High Sierra. To update a Mac 4,1 to High Sierra, you must upgrade its firmware to 5,1 to be able to install High Sierra.

Happily, you are halfway to the firmware upgrade though having already disabled SIP. Start by downloading the Mac Pro EFI Update directly from Apple and Hackintosh guru Netkas's Firmware Update Tool from his forum (first post).

Basically you make sure the disk image is mounted and then double click the Firmware Update Tool. After installing the firmware update, it's important to press the start button extra long when restarting until the power light starts blinking. You'll hear a long bong within 30 seconds and then you'll watch a grey screen where a firmware update installs along the bottom.

Which OS to Install: El Capitan, Sierra or High Sierra?

Now that you have a working and tested good silver tower, you could choose to install El Capitan, Sierra or High Sierra. El Capitan is the most reliable and solid of the recent Mac OS releases. From Sierra on, you should forget about any kind of Apple Soft Raid (old Apple Soft Raid arrays should continue to work but you'll have no tools to manage them). In these days of 2 TB SSD with read/write speeds in excess of 500 MB/sec there's little point to soft raid arrays. So for the sake of your data integrity and sanity, please remove any advanced disk configuration and go to a simpler layout following Apple's guidelines (large fast boot drive). It will cost you a few hundred dollars for the big SSD but Apple charges $1800 for 2 TB of internal SSD so enjoy the bargain.

If you choose High Sierra 10.3 there's one more essential step you have to take to enjoy (relatively) trouble free computing and that's to install High Sierra with APFS disabled. APFS is the new file system to replace the now twenty year old HFS+.

Why you would want to avoid APFS

While HFS+ has lots of issues, such as missing data checksums, nanosecond timestamps and concurrent access, HFS+ is twenty years old. The bugs have been worked out. No bugs is essential for a file system. It's not that I don't prefer APFS. It's that I will wait at least two full production years (probably three) before deploying APFS on critical data.

If you avoid both Apple Soft Raid arrays and APFS, High Sierra is not that much less stable than El Capitan.

Mailmate Eliminates Apple Mail as a Potential Spoiler

I suggest moving to High Sierra only having already moved from Apple Mail to Mailmate for email as my main driver (I live in email). I moved to Mailmate for the Markdown composition. I stay in Mailmate for the stability between OS X versions and the speed. If you are an ex-Eudora junkie or a serious email warrior (hundreds of mails read and dozens answered per day), I cannot recommend Mailmate highly enough. Serious Apple Mail users should reflect seriously on the issues introduced by Sierra and High Sierra before upgrading beyond El Capitan.

I also do not use any of the following software or services:

iCloud
iTunes
Safari

The last one (Safari) is not quite true: I do use Safari as an auxiliary browser for some multimedia like Netflix for 1080p playback and even that not on silver towers but on a MBP 2011: Chromium and Opera are my work browsers. Not being dependent on Apple software or services allows me to choose my OS based on productivity and lack of bugs rather than on Apple's plans for me. The less often you must change your OS, the more productive you will be. Each change of OS and upgrade or reinstall comes with its own headaches, potentially whole days spent troubleshooting software conflicts and bugs.

The best step you can take to reduce your IT burden is to upgrade your Apple OS only every three versions (I went from 10.6.8 to 10.11.5, that's five versions and seven productive years with the same almost bug free OS).

How to Install High Sierra without APFS

APFS installs itself by default on any flash storage or SSD drive with any High Sierra install. You have no choice. Unfortunately the APFS conversion of drives can leave you locked out of your data, with no path back in. All users should have backups (make sure you do) before they do any upgrades and should be doing complete backups at least once/week. Should and do are often two separate concepts though.

Here's some real world experience:

I've used APFS for about 3 months, this is what I got:

1) Finder unable to correctly calculate and report empty space.
2) Slow boot when TRIM activated
3) Finder micro freeze
4) Bootcamp apps in Windows unable to selected APFS as next boot partition
5) Few APFS related KP (seems fixed in the later High Sierra)
6) No RAID / Fusion support
7) Causing About This Mac -> Storage very slow on getting the space analysis

APFS allow the files breakdown into lots of small fragments. This seems no a big deal for SSD, because the latency is so low on the SSD. However, the OS still need to make more CPU I/O call to read a single file, which does induce more latency, in other words, slower.

Fortunately, the engineers inside Apple and senior executives don't want to test APFS on their primary computers either. So there's a back door to install High Sierra without APFS on flash media. A HFS+ install made with these flags appears to be safe against automated APFS conversion which has left many users without access to their data.

Here's how you do it. First download High Sierra to your Mac from the App Store (or copy the installer over to the Applications folder from another computer to avoid another download of the 5.3 GB file). Make sure the installer is in your Applications folder first.

First, you'll have to click the installer normally. You'll get a message that a firmware update is required before installing High Sierra.

Go ahead and follow the instructions for the firmware update. Your computer will restart normally after the firmware update.

This time, instead of clicking on the 'Install macOS High Sierra.app' icon, run a terminal command instead:

To install High Sierra to another volume, it would be this command:

I was not able to get the --volume directive to work so instead I fired up SuperDuper and copied my Sierra disk with the High Sierra installer over to a second SSD. I then restarted from the copied version (to be sure I had two working disks). With firmware fix applied, the first command to install High Sierra on the boot drive but without APFS worked perfectly.

Preparing Healthy Target OS Disks

You may have difficulty with your target install disk. Make sure that the partitions are healthy first. Your disk must be HFS+ Extended with a GUID partition. You do this by opening up Disk Utility and clicking First Aid from the window bar. If First Aid offers an error message, it's easier to fix the disk in either another Mac. Either way, open up terminal and run first: diskutility --verifyDisk disk2 (you can get the disk number from Disk Utility). If you get a failure message again, you should run diskutility --repairDisk disk2 (same number as above). Make sure you have the right number as you might end up erasing your disk. After repair, verify again. If that doesn't work, you'll have to erase the disk once or twice until you can finally run First Aid and verifyDisk with no errors.

Multimedia Applications on High Sierra

I've successfully run Final Cut Pro X 10.3.4 and 10.4.1 on High Sierra, as well as photo programs like Fast Raw Viewer, Iridient Developer. Basics like BBEdit and iAWriter work just fine. Simple music players like Clementine and Decibel work equally well. I've heard that there are some under the hood audio changes which affect pro audio programs so you must double check your key applications before upgrading if you are an advanced audio creator. Legacy Adobe users should know some issues with Adobe Creative Suite CS6 creep in after El Capitan (InDesign is the most troubled).

Viable Reasons to install High Sierra on production computers

FCPX

The reason I moved to High Sierra on my multimedia 12 core computer (I never run the latest release) is to enjoy the significantly better colour correction in FCPX 10.4.1. Sadly there are major bugs in the colour corrector in 10.4.0 which is the last FCPX which runs on Sierra. Apple's lack of courtesy to pro users inexplicable to me - Apple won't fix FCPX for Sierra. Forcing pro users onto the latest OS is deeply wrong, as pro users need complex programs which may not yet have stable versions available to run on the latest version of OS X.

My productivity computers still run 10.11 (El Capitan).

Software Testing and Latest iOS Support in Xcode

In Foliovision, we are upgrading one of our support computers to High Sierra so that we can do testing on the latest Safari for our own video player.

Our main programmer Martin is considering upgrading to High Sierra as there are some good simulators for the latest iOS version in current Xcode. Martin tries to shift OS only ever couple of versions to avoid the inevitable downtime brought on by fighting upgrade bugs.

Tighter Integration with iDevices

This doesn't apply to most of us. We don't use the Apple services like iCloud (Jennifer Lawrence's very private photos along with the other victims of fappening was lesson enough to us that keeping our personal data on a platform which can be easily defeated via social engineering such as iCloud would just be foolishness). Our team in the marketing department disagree and love all of their MBP 13', iPhones from 5se to 7 Plus and their Apple services with nary a care for privacy and/or security. For some reason, they've collectively decided to distrust Facebook but trust Apple. Little Red Riding Hood still talks with wolves all these centuries later.

This group don't use advanced features or much shareware. They plug along with Apple pre-installed software (plus Affinity Photo/Affinity Designer) and mainly without multi-clipboards, text expanders and macros. If you are not an advanced user, you are probably not using most of the features Apple keeps breaking and you don't much care one way or another if features come and go to sell the latest OS. You've already moved on with whatever you are given. You probably never figured out the last set of advanced Apple features so you don't miss it when it disappears or radically changes.

In the post-Jobs epoch of annual OS upgrades and disappearing and dumbed down Apple software, most Apple users would be better served by finding third party software built by dedicated developers and staying on a single OS for three cycles (depends on quality of releases of course). The same applies to iOS. Far better to refuse those nagging updates and stay productive than keep running on what has become an endless update hamster wheel.

Game breaker with Sierra and High Sierra: Advanced Networking

Networking doesn't really work properly any more. You can't allow screen sharing access or file sharing on a computer running High Sierra without disabling Apple's Firewall. Disabling the Firewall is a much, much worse security hole than not having SIP enabled. You do not want people outside your network to easily ping and access your Mac (most consumer routers are just detritus in the way of an experienced hacker).

Any computer which you want to work as a file server should not be running High Sierra. Think of Kodi or Plex for instance.

Revisiting the OS Choice

For a productivity computer, OS X 10.11 El Capitan is your best choice. There are the least number of issues with El Capitan of the three current OS. Almost all software still works with El Capitan. For most multimedia computers, I'd recommend OS X 10.11 (Davinci Resolve 14 users have official support for OS X 10.12 only but Resolve runs fine on 10.11, apart from HEVC encoding). Adobe CC users probably want to stay with El Capitan for now. If you just want HEVC for Resolve then Sierra would be your best choice as Resolve shows more bugs with High Sierra.

For a FCPX user, High Sierra should be preferred for the vastly improved colour correction. For a general user, if you must move beyond El Capitan, I recommend jumping straight to High Sierra just to save yourself the hassle of upgrading the OS twice within a year. At 10.13.5 with 10.14 Mojave already in public beta, High Sierra is relatively mature (if still buggy) and its inadequacies have been clearly charted.

Alec has been helping businesses succeed online since 2000. Alec is an SEM expert with a background in advertising, as a former Head of Television for Grey Moscow and Senior Television Producer for Bates, Saatchi and Saatchi Russia.

Path: /Applications/clementine.app/Contents/MacOS/clementine

Version: 1.3.1 (4096.1.3.1.1)

Parent Process: ??? [1]

User ID: xxxxxxxxxxxxx

Date/Time: 2018-09-25 10:44:05.959 +0200

Report Version: 12

Time Awake Since Boot: 930 seconds

System Integrity Protection: disabled

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Type: EXC_BAD_ACCESS (SIGSEGV)

Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000

Termination Reason: Namespace SIGNAL, Code 0xb

-->

__TEXT 000000010ec79000-000000010fad8000 [ 14.4M] r-x/rwx SM=COW /Applications/clementine.app/Contents/MacOS/clementine

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread

0 com.apple.CoreFoundation 0x00007fff2dcb2542 CFMachPortIsValid + 14

1 com.apple.CoreFoundation 0x00007fff2dcb260a CFMachPortCreateRunLoopSource + 72

2 org.clementine-player.clementine0x000000010f1b459c -[SPMediaKeyTap startWatchingMediaKeys] + 92

3 com.apple.CoreFoundation 0x00007fff2dd00076 __CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER__ + 12

4 com.apple.CoreFoundation 0x00007fff2dcffff0 ___CFXRegistrationPost_block_invoke + 63

5 com.apple.CoreFoundation 0x00007fff2dcfff11 _CFXRegistrationPost + 398

6 com.apple.CoreFoundation 0x00007fff2dd0824d ___CFXNotificationPost_block_invoke + 87

7 com.apple.CoreFoundation 0x00007fff2dc6f3a4 -[_CFXNotificationRegistrar find:object:observer:enumerator:] + 1804

8 com.apple.CoreFoundation 0x00007fff2dc6e649 _CFXNotificationPost + 854

9 com.apple.Foundation 0x00007fff3000ebab -[NSNotificationCenter postNotificationName:object:userInfo:] + 66

10 com.apple.AppKit 0x00007fff2b1eac42 -[NSApplication _postDidFinishNotification] + 313

11 com.apple.AppKit 0x00007fff2b1ea566 -[NSApplication _sendFinishLaunchingNotification] + 209

12 com.apple.AppKit 0x00007fff2b1e7ec0 -[NSApplication(NSAppleEventHandling) _handleAEOpenEvent:] + 552

13 com.apple.AppKit 0x00007fff2b1e7b0f -[NSApplication(NSAppleEventHandling) _handleCoreEvent:withReplyEvent:] + 690

14 com.apple.Foundation 0x00007fff30059274 -[NSAppleEventManager dispatchRawAppleEvent:withRawReply:handlerRefCon:] + 287

15 com.apple.Foundation 0x00007fff300590f0 _NSAppleEventManagerGenericHandler + 102

16 com.apple.AE0x00007fff2ef43b6b aeDispatchAppleEvent(AEDesc const*, AEDesc*, unsigned int, unsigned char*) + 1855

17 com.apple.AE0x00007fff2ef433d5 dispatchEventAndSendReply(AEDesc const*, AEDesc*) + 41

18 com.apple.AE0x00007fff2ef432ad aeProcessAppleEvent + 439

19 com.apple.HIToolbox 0x00007fff2cf3003e AEProcessAppleEvent + 55

20 com.apple.AppKit 0x00007fff2b1e3c3c _DPSNextEvent + 1734

21 com.apple.AppKit 0x00007fff2b1e26fa -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1362

22 com.apple.AppKit 0x00007fff2b1dc75d -[NSApplication run] + 699

23 QtGui 0x000000011120992a QEventDispatcherMac::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) + 554

24 QtCore 0x0000000111eb37ea QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) + 394

Mac Os Mojave Requirements

25 QtCore 0x0000000111eb6067 QCoreApplication::exec() + 199

26 org.clementine-player.clementine0x000000010ec883a4 main + 5620

0 libsystem_pthread.dylib 0x00007fff5afba408 start_wqthread + 0

0 libsystem_kernel.dylib 0x00007fff5af08e82 __select + 10

1 com.apple.CoreFoundation 0x00007fff2dcc9a59 __CFSocketManager + 634

2 libsystem_pthread.dylib 0x00007fff5afbb33d _pthread_body + 126

3 libsystem_pthread.dylib 0x00007fff5afbe2a7 _pthread_start + 70

4 libsystem_pthread.dylib 0x00007fff5afba425 thread_start + 13

Thread 7:: Thread (pooled)

0 libsystem_kernel.dylib 0x00007fff5af051b2 __psynch_cvwait + 10

1 libsystem_pthread.dylib 0x00007fff5afbe5cb _pthread_cond_wait + 724

2 QtCore 0x0000000111dd16d3 QWaitConditionPrivate::wait(unsigned long) + 211

3 QtCore 0x0000000111dd14ba QWaitCondition::wait(QMutex*, unsigned long) + 218

4 QtCore 0x0000000111dc5495 QThreadPoolThread::run() + 613

5 QtCore 0x0000000111dcffaa QThreadPrivate::start(void*) + 410

6 libsystem_pthread.dylib 0x00007fff5afbb33d _pthread_body + 126

7 libsystem_pthread.dylib 0x00007fff5afbe2a7 _pthread_start + 70

8 libsystem_pthread.dylib 0x00007fff5afba425 thread_start + 13

Thread 8:: QThread

0 libsystem_kernel.dylib 0x00007fff5af08e82 __select + 10

1 QtCore 0x0000000111edb6b4 qt_safe_select(int, fd_set*, fd_set*, fd_set*, timeval const*) + 452

2 QtCore 0x0000000111eddca1 QEventDispatcherUNIXPrivate::doSelect(QFlags<QEventLoop::ProcessEventsFlag>, timeval*) + 801

3 QtCore 0x0000000111edf633 QEventDispatcherUNIX::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) + 227

4 QtCore 0x0000000111eb37ea QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) + 394

6 QtCore 0x0000000111dcffaa QThreadPrivate::start(void*) + 410

7 libsystem_pthread.dylib 0x00007fff5afbb33d _pthread_body + 126

8 libsystem_pthread.dylib 0x00007fff5afbe2a7 _pthread_start + 70

9 libsystem_pthread.dylib 0x00007fff5afba425 thread_start + 13

Thread 9:: QProcessManager

0 libsystem_kernel.dylib 0x00007fff5af08e82 __select + 10

1 QtCore 0x0000000111e92077 QProcessManager::run() + 135

2 QtCore 0x0000000111dcffaa QThreadPrivate::start(void*) + 410

3 libsystem_pthread.dylib 0x00007fff5afbb33d _pthread_body + 126

4 libsystem_pthread.dylib 0x00007fff5afbe2a7 _pthread_start + 70

5 libsystem_pthread.dylib 0x00007fff5afba425 thread_start + 13

Thread 10:: QThread

0 libsystem_kernel.dylib 0x00007fff5af08e82 __select + 10

1 QtCore 0x0000000111edb6b4 qt_safe_select(int, fd_set*, fd_set*, fd_set*, timeval const*) + 452

2 QtCore 0x0000000111eddca1 QEventDispatcherUNIXPrivate::doSelect(QFlags<QEventLoop::ProcessEventsFlag>, timeval*) + 801

3 QtCore 0x0000000111edf633 QEventDispatcherUNIX::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) + 227

4 QtCore 0x0000000111eb37ea QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) + 394

6 QtCore 0x0000000111dcffaa QThreadPrivate::start(void*) + 410

7 libsystem_pthread.dylib 0x00007fff5afbb33d _pthread_body + 126

Clementine Mac Os Mojave Dmg

8 libsystem_pthread.dylib 0x00007fff5afbe2a7 _pthread_start + 70

9 libsystem_pthread.dylib 0x00007fff5afba425 thread_start + 13

Thread 11:: QThread