When I connect my SD cards to it, Final Cut Pro 10.4 crashes. When I try to relaunch, it opens and then closes again. What is wrong?
MacBook Pro TouchBar and Touch ID, macOS High Sierra (10.13.2)
No idea what's wrong (other than 10.4 is turning into a kludge) but as a work around you could try manually importing everything to a folder on your HDD by either dragging & dropping or using Image Capture, then, from FCP, importing from the folder.
Not sure why this happened, but whenever there is a crash you should delete your preferences. Preferences can become corrupted as the result of the crash, and that in turn can cause further crashes.
To delete preferences, hold down command and option while starting FCP X and click "Delete Preferences".
You will have to open your library, but this does not delete any of your content.
After messing with this for the last couple of hours I've discovered that 10.4 will crash if I have *any* kind of external device plugged in including an SD card. If I disconnect my external drives, my DVD burner and my SD card it works. As soon as I plug in *any* of those things and try to launch FCP 10.4 it will crash constantly.
This must be a hardware problem. Thousands of users around the world are working with the application with external drives connected. I am right now.
Could you give your system specs and your layout? Is there a hub attached?
It's happening on two machines? Trying to guess here what you're trying to say in short hand.
This isn't happening to any other user on this forum with either of these machines. No crashing because external devices are connected. Suspect you have something installed on both machines that's has a serious system conflict. Perhaps you've run some bad virus clean up software that's hosed your system. Probably need to do a clean install of the system and rebuild the software.
I have the same problem. Final Cut 4 crashes immediately on starting up. So does Motion. Compressor works.
I have been through the whole gamut of reinstalling the software, external drives off, trashing preferences, forcing it to start up without accessing a library, trashing the plugin folders etc. Still no luck. So I reinstalled the previous version and restored my plugins (they are now both in my application folder) and the previous version works perfectly! Weird.
It’s the latest iMac.
| Model Name: | iMac |
| Model Identifier: | iMac18,3 |
| Processor Name: | Intel Core i7 |
| Processor Speed: | 4.2 GHz |
| Number of Processors: | 1 |
| Total Number of Cores: | 4 |
| L2 Cache (per Core): | 256 KB |
| L3 Cache: | 8 MB |
| Memory: | 16 GB |
Model Name: iMac
This is the error message:
Crashed Thread: 8 Dispatch queue: NSOperationQueue 0x600001225f80 (QOS: UNSPECIFIED)
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY
Termination Signal: Segmentation fault: 11
Termination Reason: Namespace SIGNAL, Code 0xb
Terminating Process: exc handler [0]
gagf wrote:
I see - my first go at a forum really. Apologies. Should I start a new conversation elsewhere?
Ask a new question with relevant info about your system and what you do when the issue occurs.
Regards you issue:
Try creating a new User account with Admin privileges, then use that.
Al
All I know is that when I pull the SD card out it works. I've been moving the files to an external drive and importing them and it works so I'm not saying its external devices. But the my Canon CFast 2.0 and the SD card is not working.
I've encountered the same problem on my 2017 iMac. After updating Final Cut Pro X a couple of days ago the app now crashes on launch - unless I unplug all external drives attached to my machine. This is very worrying as I earn my income by editing with FCP. It was working yesterday.
Yesterday I incorrectly concluded that my external devices were causing it. It ends up there was just some coincidental occurrences in my pattern of unplugging and plugging back in my various devices. Ends up it still crashes on launch all the time, but what I've found is that if I just keep trying then usually on the 3rd or 4th attempt it'll launch and run just fine. I may even be able to launch it a few more times in a row without incident, but then it'll eventually start crashing on launch again.
I don't think it is necessarily a hardware problem. I am having random crashes since updating to 10.4. At first I thought it was related to importing, but upon further use it seems to be crashing randomly. It has crashed while sitting idle, while importing, while placing clips, etc. Launches fine and seems okay, then after using for a few minutes it crashes without warning.
I am using a late 2017 iMac running Sierra 10.12.6 with 24 gigs of RAM.
Much to my surprise, Apple contacted me directly about this problem, and after looking at my crash logs and system config file they determined it was a known problem caused by a bug in CamTwist. Apparently, some extension that CamTwist installs is not compatible with 10.4 and causes the launch crash. I deleted all CamTwist files on my hard drive, rebooted, and now things work fine.
No, I had written a poor review on the App Store. They then reached out to see what they could do.
CamTwist is a video app that is useful for live broadcasting with various bits of hardware and input sources. Things like live Facebook feeds from your Mac, etc. I haven't actually used it in many years, so no loss getting rid of it.
Hi, I have the same problem here too.
New Admin account gives me the same issue, and it's not SD card related because I didn't try importing anything.
I've tried deleting the .fcpbundle library as I no longer need the previous one but the same issue occurred.
It was definitely the 10.4 upgrade because it didn't happen to 10.3.x
Crash log snippet below.
[...]
Crashed Thread: 7 Dispatch queue: NSOperationQueue 0x60800042c900 (QOS: UNSPECIFIED)
[...]
Thread 7 Crashed:: Dispatch queue: NSOperationQueue 0x60800042c900 (QOS: UNSPECIFIED)
0 com.apple.CoreFoundation 0x00007fff2ffbaaea CFStringGetLength + 10
1 com.apple.CoreFoundation 0x00007fff2ffcd208 CFStringCompare + 24
2 com.apple.ozone.framework 0x000000011c1e1cb9 OZGetNewFontID(__CFString const*) + 41
3 com.apple.ozone.framework 0x000000011c1e3250 OZFontManager::enumerateSystemFonts() + 928
4 com.apple.ozone.framework 0x000000011c1e296b OZFontManagerBase::initFonts() + 27
5 libdispatch.dylib 0x00007fff57846d50 _dispatch_client_callout + 8
6 libdispatch.dylib 0x00007fff57846d03 dispatch_once_f + 41
7 com.apple.ozone.framework 0x000000011c1e2219 OZFontManager::getInstance() + 41
8 com.apple.ozone.framework 0x000000011c1e3f7f -[OZFontMenuImageCacheBuilder rebuildImageCache:] + 1279
9 com.apple.Motion.effect 0x000000011b7502f2 +[FFMotionEffect initializeMotionFramework] + 225
10 com.apple.Motion.effect 0x000000011b7500a5 __48+[FFMotionEffect initializeMotionAsynchronously]_block_invoke + 26
11 com.apple.Foundation 0x00007fff3212b22f __NSBLOCKOPERATION_IS_CALLING_OUT_TO_A_BLOCK__ + 7
12 com.apple.Foundation 0x00007fff3212b091 -[NSBlockOperation main] + 68
13 com.apple.Foundation 0x00007fff3212953e -[__NSOperationInternal _start:] + 778
14 libdispatch.dylib 0x00007fff57846d50 _dispatch_client_callout + 8
15 libdispatch.dylib 0x00007fff57859333 _dispatch_block_invoke_direct + 317
16 libdispatch.dylib 0x00007fff57846d50 _dispatch_client_callout + 8
17 libdispatch.dylib 0x00007fff57859333 _dispatch_block_invoke_direct + 317
18 libdispatch.dylib 0x00007fff578591d6 dispatch_block_perform + 109
19 com.apple.Foundation 0x00007fff3212554c __NSOQSchedule_f + 342
20 libdispatch.dylib 0x00007fff57846d50 _dispatch_client_callout + 8
21 libdispatch.dylib 0x00007fff57859e76 _dispatch_continuation_pop + 472
22 libdispatch.dylib 0x00007fff578516cb _dispatch_async_redirect_invoke + 703
23 libdispatch.dylib 0x00007fff57848941 _dispatch_root_queue_drain + 515
24 libdispatch.dylib 0x00007fff578486ed _dispatch_worker_thread3 + 101
25 libsystem_pthread.dylib 0x00007fff57b0b1ca _pthread_wqthread + 1387
26 libsystem_pthread.dylib 0x00007fff57b0ac4d start_wqthread + 13
[...]
Model: MacBookPro11,3, BootROM MBP112.0142.B00, 4 processors, Intel Core i7, 2.3 GHz, 16 GB, SMC 2.19f12
Graphics: Intel Iris Pro, Intel Iris Pro, Built-In
Graphics: NVIDIA GeForce GT 750M, NVIDIA GeForce GT 750M, PCIe, 2 GB
Memory Module: BANK 0/DIMM0, 8 GB, DDR3, 1600 MHz, 0x80AD, 0x484D54343147533641465238412D50422020
Memory Module: BANK 1/DIMM0, 8 GB, DDR3, 1600 MHz, 0x80AD, 0x484D54343147533641465238412D50422020
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x134), Broadcom BCM43xx 1.0 (7.77.37.5.1a3)
Bluetooth: Version 6.0.2f2, 3 services, 27 devices, 1 incoming serial ports
Network Service: Wi-Fi, AirPort, en0
Serial ATA Device: APPLE SSD SM0512F, 500.28 GB
USB Device: USB 3.0 Bus
USB Device: Apple Internal Keyboard / Trackpad
USB Device: BRCM20702 Hub
USB Device: Bluetooth USB Host Controller
Thunderbolt Bus: MacBook Pro, Apple Inc., 17.1
I've got a different "report to apple" dialogue earlier and some code crashed because month = 13 (Seems to be what I've highlighted in red above). But I've changed the date of my Mac to January and it still crashed.
Final Cut Pro 10.4 Crashes
