fbpx
Welcome, Guest
Username: Password: Remember me
  • Page:
  • 1
  • 2

TOPIC: [CRASH] FCPX 10.3 Import Error

[CRASH] FCPX 10.3 Import Error 19 Jan 2017 19:39 #84986

  • agam.yunus
  • agam.yunus's Avatar Topic Author
  • Offline
  • Fresh Boarder
  • Fresh Boarder
  • Posts: 10
  • Thank you received: 0
Hi,

My FCPX quit unexpectedly every time I tried to import media or create a new project. I'm running 10.3. 1. But 10.2.3 runs just fine. I would like to take the advantage of the new features of 10.3.

I've tried:
- Deleting FCPX preferences
- Using AppCleaner to uninstall FCPX and reinstall it back
- Tried to import different rushes from both Internal and External drives
- Create new library
- Create new mac admin account

I'm running Sierra 10.12.2

None of the above succeeded.

Does anyone have the same problem before and perhaps have the solution to fix the problem?

Thanks in advance :)

Please Log in or Create an account to join the conversation.

Last edit: by agam.yunus.

[CRASH] FCPX Import Error 20 Jan 2017 16:55 #85048

  • agam.yunus
  • agam.yunus's Avatar Topic Author
  • Offline
  • Fresh Boarder
  • Fresh Boarder
  • Posts: 10
  • Thank you received: 0

agam.yunus wrote: Hi,

My FCPX quit unexpectedly every time I tried to import media or create a new project. I'm running 10.3. 1. But 10.2.3 runs just fine. I would like to take the advantage of the new features of 10.3.

I've tried:
- Deleting FCPX preferences
- Using AppCleaner to uninstall FCPX and reinstall it back
- Tried to import different rushes from both Internal and External drives
- Create new library
- Create new mac admin account

I'm running Sierra 10.12.2

None of the above succeeded.

Does anyone have the same problem before and perhaps have the solution to fix the problem?

Thanks in advance :)


Anyone here might know how to fix this issue?

Please Log in or Create an account to join the conversation.

[CRASH] FCPX Import Error 22 Jan 2017 11:18 #85081

  • joema
  • joema's Avatar
  • Offline
  • Platinum Boarder
  • Platinum Boarder
  • Posts: 1558
  • Karma: 27
  • Thank you received: 334
I had what may be this problem on 10.3.1. FCPX started crashing immediately on trying to import any file -- whenever the import dialog came up, before even clicking on a file. Each time the crashing thread's call stack was the same; see below.

I was on the phone with Apple support for two days and they remotely tried to diagnose the problem -- unsuccessfully. Corrective steps included running disk First Aid, reinstalling macOS, reinstalling FCPX, trashing FCPX preferences, resetting SMC and NVRAM, and logging in as another user. It still crashed.

I tried erasing and rolling back the hard drive several days using Time Machine -- it still crashed. I then erased the hard drive and loaded a month-old disk clone from Carbon Copy -- it still crashed. I then took the machine to the local Apple Store and they ran overnight hardware diagnostics, with no problem found.

Apple then said my only option was erase the disk and reinstall every app, plugin and file. They were not willing to analytically debug the problem any further, despite having gathered a lot of diagnostic data using special monitoring tools. I told them without understanding what went wrong I could be later afflicted again or some other user. No number of backups will prevent this situation.

Apple speculated that somehow months ago some files got damaged or corrupted which affected FCPX and whatever those files were, they were not replaced by reinstalling macOS or FCPX "in place".

I explained this was a very serious problem because it cannot be fixed by any backup system and reinstalling every app, utility and plugin will take days. However that is all Apple was willing to do.

After erasing and reinstalling all apps, files and plugins, FCPX is running OK so far, now on 10.3.2. Obviously if 10.3.2 had been available before this happened I would have tried that.

This was a bad and costly experience. As a former escalation support engineer at another large software company, I would have at least examined the call stack, did a full-text search comparing it to all other reports, and examined the source code and possible code path fan-in leading to this condition. In some cases I would have built an instrumented version of the product to gather more detailed data surrounding the crash. However this case was also amenable to live remote debugging since it happens immediately with 100% reliability.

Thread 20 Crashed:: Dispatch queue: NSOperationQueue 0x600001231b00 :: NSOperation 0x60000124cb10 (QOS: USER_INTERACTIVE)
0 libsystem_kernel.dylib 0x00007fffb229bdd6 __pthread_kill + 10
1 libsystem_pthread.dylib 0x00007fffb2387787 pthread_kill + 90
2 libsystem_c.dylib 0x00007fffb2201420 abort + 129
3 com.apple.Flexo 0x000000010560c594 FFApplicationHandleExceptionThatShouldNotBeIgnored + 452
4 com.apple.CoreFoundation 0x00007fff9cd1dd5a __handleUncaughtException + 746
5 libobjc.A.dylib 0x00007fffb188bf15 _objc_terminate() + 94
6 libc++abi.dylib 0x00007fffb0d7ed69 std::__terminate(void (*)()) + 8
7 libc++abi.dylib 0x00007fffb0d7ede3 std::terminate() + 51
8 libdispatch.dylib 0x00007fffb21370cc _dispatch_client_callout + 28
9 libdispatch.dylib 0x00007fffb214dae5 _dispatch_queue_serial_drain + 896
10 libdispatch.dylib 0x00007fffb213fcd9 _dispatch_queue_invoke + 1046
11 libdispatch.dylib 0x00007fffb2138e70 _dispatch_root_queue_drain + 476
12 libdispatch.dylib 0x00007fffb2138c47 _dispatch_worker_thread3 + 99
13 libsystem_pthread.dylib 0x00007fffb2384712 _pthread_wqthread + 1299
14 libsystem_pthread.dylib 0x00007fffb23841ed start_wqthread + 13

Please Log in or Create an account to join the conversation.

Last edit: by joema.

[CRASH] FCPX 10.3 Import Error 22 Jan 2017 12:24 #85085

  • FCPX.guru
  • FCPX.guru's Avatar
  • Offline
  • Platinum Boarder
  • Platinum Boarder
  • bbalser.com
  • Posts: 3601
  • Karma: 34
  • Thank you received: 499
Not with importing, but when working heavily with multicam clips, 10.3.2 is now crashing a LOT.

Please Log in or Create an account to join the conversation.

[CRASH] FCPX Import Error 22 Jan 2017 17:54 #85093

  • agam.yunus
  • agam.yunus's Avatar Topic Author
  • Offline
  • Fresh Boarder
  • Fresh Boarder
  • Posts: 10
  • Thank you received: 0
Hi @joema,

Thanks a lot for your response and the detailed story. That's true erasing the disk and reinstalling all the program would be suck. But I would give it a go, since 10.3.2 trial still not available at the moment.

I hope by doing so, it will fix the problem and FCPX could run smoothly. I'll post the update once I'm done.

Thanks once again and wish me luck :)

Please Log in or Create an account to join the conversation.

[CRASH] FCPX Import Error 24 Jan 2017 18:08 #85148

  • agam.yunus
  • agam.yunus's Avatar Topic Author
  • Offline
  • Fresh Boarder
  • Fresh Boarder
  • Posts: 10
  • Thank you received: 0
Hi Joema,

Thanks for your helpful informations.

Unfortunately, FCPX 10.3 still not working on my computer. I've tried installing 10.3.2 and update Sierra to 10.12.3 but still no luck. I guess I have to wait until 10.4 release.

I'm still not sure what caused the errors. I even tried to format my disk and reinstall OSX Sierra 3 times :( Hopefully someone in this forum could give another solutions to the problem.

Thanks again! :)

Please Log in or Create an account to join the conversation.

[CRASH] FCPX Import Error 24 Jan 2017 19:22 #85149

  • joema
  • joema's Avatar
  • Offline
  • Platinum Boarder
  • Platinum Boarder
  • Posts: 1558
  • Karma: 27
  • Thank you received: 334

agam.yunus wrote: Hi Joema,

Thanks for your helpful informations.

Unfortunately, FCPX 10.3 still not working on my computer. I've tried installing 10.3.2 and update Sierra to 10.12.3 but still no luck. I guess I have to wait until 10.4 release...


This probably will not be fixed in 10.4 because Apple declined to pursue the problem, despite my firm request. We don't even know for sure that FCPX is at fault.

If your problem is like mine, *none* of these steps will fix it:

- Reinstalling FCPX and macOS (in place)
- Trashing preferences
- Using a different login
- Removing macOS plist files or non-essential kernel extensions
- Running disk First Aid
- Resetting SMC/NVRAM
- Erasing boot drive and loading a month-old clone backup

It is a condition whereby FCPX 10.3.x crashes immediately upon launching the import dialog, before even reaching the media file. The cause is unknown, but in my case the stack trace of the crashing thread was always the same (see above). The call stack indicates a Grand Central Dispatch setup for a serial queue, which is often use to synchronize access to a "critical section" (a data structure or object which does not permit concurrent access). It then appears the OS made an async callback to the client code (ie FCPX), which then crashed.

In my case fixing the problem required erasing the hard drive and installing macOS, FCPX, and every app, utility and plugin. Since many of the higher-end items are individually authenticated this sometimes required corresponding with each vendor. This took several days. There is no guarantee it won't happen again, since Apple did not pursue this.

In your case 10.2.3 seems to run so you can stay on that. I already had a lot of work invested on 10.3.1, so I couldn't easily go back. To stay on 10.3.x, you might have to erase and reinstall everything like I did.

If you can look up the call stack of the crashing FCPX thread, that might help determine whether it's the same problem as mine. That is in the Console utility under User Reports; look for what FCPX thread crashed and post that one call stack.

Please Log in or Create an account to join the conversation.

[CRASH] FCPX Import Error 25 Jan 2017 06:43 #85163

  • agam.yunus
  • agam.yunus's Avatar Topic Author
  • Offline
  • Fresh Boarder
  • Fresh Boarder
  • Posts: 10
  • Thank you received: 0
Hi @joema,

As you suggested, here's my crash report on FCPX 10.3.2. Sorry, but I have no clue on how to identify the problem from the report. :unsure:

System Integrity Protection: enabled

Crashed Thread: 17 BGTask: MEBackgroundLoadManager Dispatch queue: NSOperationQueue 0x61800063faa0 :: NSOperation 0x61800015b800 (QOS: USER_INITIATED)

Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY

Application Specific Information:
[FFHGRendererInfo initWithLocation:] CGLSetVirtualScreen failed - didn't expect to get here. Investigate why this code ran: [FFHGRendererInfo initWithLocation:] CGLSetVirtualScreen failed: loc=1, ctxt=0x7fcf9e1ea200, err=10008
abort() called

Application Specific Backtrace 1:
0 CoreFoundation 0x00007fffd30e1e7b __exceptionPreprocess + 171
1 libobjc.A.dylib 0x00007fffe7ccbcad objc_exception_throw + 48
2 CoreFoundation 0x00007fffd30e6b82 +[NSException raise:format:arguments:] + 98
3 Foundation 0x00007fffd4b30d50 -[NSAssertionHandler handleFailureInMethod:object:file:lineNumber:description:] + 195
4 Flexo 0x0000000101d1991b -[FFRendererInfo initWithLocation:] + 587
5 Flexo 0x0000000101d1aebd -[FFHGRendererManager _setupRenderers] + 109
6 Flexo 0x0000000101d1afb6 -[FFHGRendererManager _ensureRenderersSetup] + 54
7 Flexo 0x0000000101d1be99 -[FFHGRendererManager canFitTextureWithBounds:] + 345
8 Flexo 0x0000000101b9f8c4 -[FFProviderCG nativeVideoProps] + 2308
9 ProMedia 0x000000010f3ac7f3 _Z8CG_Open2RK19PMFormatDescriptionRK5PCURLP12CGColorSpaceP14CGInstanceData + 1203
10 ProMedia 0x000000010f3ae9f4 _Z7CG_OpenRK19PMFormatDescriptionRK5PCURLPPv + 308
11 ProMedia 0x000000010f393fb1 _ZN6PMClip4openEv + 177
12 ProMedia 0x000000010f39b19a _ZN14PMMediaManager4openERK5PCURLPP6PMClipP17PMPluginInterfaceb + 154
13 Ozone 0x000000010d50a8b9 _ZN9OZFootage7openURLERK5PCURLbb + 57
14 Ozone 0x000000010d50bc42 _ZN9OZFootage9openMediaEv + 674
15 Ozone 0x000000010d4d0c09 _ZN7OZScene9openMediaEv + 457
16 MotionEffect 0x000000010d0bdda0 -[FFMotionEffect loadEffectValues:] + 131
17 MotionEffect 0x000000010d0bdb0c -[FFMotionEffect _makeLoadedDocReady] + 698
18 MotionEffect 0x000000010d0bbb5c -[FFMotionEffect _backgroundLoadDocument:onTask:] + 1007
19 Flexo 0x0000000101c4c683 -[FFBackgroundLoadManager _backgroundTask:onTask:] + 323
20 Flexo 0x00000001026b5d7c FFApplicationHandleExceptionThatShouldNotBeIgnoredInBlock + 12
21 Flexo 0x0000000101d0c473 -[FFBackgroundTask main] + 499
22 Foundation 0x00007fffd4a8c6e4 -[__NSOperationInternal _start:] + 672
23 Foundation 0x00007fffd4a8859b __NSOQSchedule_f + 201
24 libdispatch.dylib 0x00007fffe85790b8 _dispatch_client_callout + 8
25 libdispatch.dylib 0x00007fffe858fae5 _dispatch_queue_serial_drain + 896
26 libdispatch.dylib 0x00007fffe8581cd9 _dispatch_queue_invoke + 1046
27 libdispatch.dylib 0x00007fffe857ae70 _dispatch_root_queue_drain + 476
28 libdispatch.dylib 0x00007fffe857ac47 _dispatch_worker_thread3 + 99
29 libsystem_pthread.dylib 0x00007fffe87c6712 _pthread_wqthread + 1299
30 libsystem_pthread.dylib 0x00007fffe87c61ed start_wqthread + 13

Please Log in or Create an account to join the conversation.

[CRASH] FCPX Import Error 25 Jan 2017 19:03 #85180

  • joema
  • joema's Avatar
  • Offline
  • Platinum Boarder
  • Platinum Boarder
  • Posts: 1558
  • Karma: 27
  • Thank you received: 334
Well that is definitely a different backtrace from mine, however I'm not sure the backtrace is from the crashed thread. At the top it says:

Crashed Thread: 17 BGTask: MEBackgroundLoadManager

That means the top of the stack for thread 17 (the crashed thread) should be in that function, but it's not in the backtrace you posted, which indicates that's not the right thread. You'll need to scroll down through the console log and copy/paste only the actual thread backtrace that crashed -- thread 17 in this case.

Also is this the crash from just trying to import a file? If so does it crash immediately when reaching the import dialog or not until you click on a file? Is the stack trace from the crashing thread the same each time?

We want the simplest possible reproducible case. E.g, if it happens consistently when trying to import a file, does that happen on a single test library with all other libraries closed? Does it happen with any media, only some media, or does it crash before even accessing the media?

Please Log in or Create an account to join the conversation.

[CRASH] FCPX Import Error 25 Jan 2017 19:26 #85182

  • agam.yunus
  • agam.yunus's Avatar Topic Author
  • Offline
  • Fresh Boarder
  • Fresh Boarder
  • Posts: 10
  • Thank you received: 0
Hi @joema

The crash i'm experiencing from 10.3.x is when I'm importing a file or create a new project.

When I try to import, it brings out the import dialog box, but it closes as soon as I click on a footage that I want to import. Yes, I've tried importing different formats of footages from different location (desktop, internal SATA, external HD). None of them works so far. I tried creating several new library in different locations but it also gives me the same errors.

Here's the crash report from Thread 17 (from earlier post).

Thread 17 Crashed:: BGTask: MEBackgroundLoadManager Dispatch queue: NSOperationQueue 0x61800063faa0 :: NSOperation 0x61800015b800 (QOS: USER_INITIATED)
0 libsystem_kernel.dylib 0x00007fffe86dddd6 __pthread_kill + 10
1 libsystem_pthread.dylib 0x00007fffe87c9787 pthread_kill + 90
2 libsystem_c.dylib 0x00007fffe8643420 abort + 129
3 com.apple.Flexo 0x00000001026b5d44 FFApplicationHandleExceptionThatShouldNotBeIgnored + 452
4 com.apple.Flexo 0x00000001026b5d90 FFApplicationHandleExceptionThatShouldNotBeIgnoredInBlock + 32
5 com.apple.Flexo 0x0000000101d0c473 -[FFBackgroundTask main] + 499
6 com.apple.Foundation 0x00007fffd4a8c6e4 -[__NSOperationInternal _start:] + 672
7 com.apple.Foundation 0x00007fffd4a8859b __NSOQSchedule_f + 201
8 libdispatch.dylib 0x00007fffe85790b8 _dispatch_client_callout + 8
9 libdispatch.dylib 0x00007fffe858fae5 _dispatch_queue_serial_drain + 896
10 libdispatch.dylib 0x00007fffe8581cd9 _dispatch_queue_invoke + 1046
11 libdispatch.dylib 0x00007fffe857ae70 _dispatch_root_queue_drain + 476
12 libdispatch.dylib 0x00007fffe857ac47 _dispatch_worker_thread3 + 99
13 libsystem_pthread.dylib 0x00007fffe87c6712 _pthread_wqthread + 1299
14 libsystem_pthread.dylib 0x00007fffe87c61ed start_wqthread + 13


This is from another error (recent attempt to open FCPX before posting to this forum), this time it shows Thread 25.

Crashed Thread: 25 Dispatch queue: com.apple.root.default-qos

Thread 25 Crashed:: Dispatch queue: com.apple.root.default-qos
0 libsystem_kernel.dylib 0x00007fff98c71dd6 __pthread_kill + 10
1 libsystem_pthread.dylib 0x00007fff98d5d787 pthread_kill + 90
2 libsystem_c.dylib 0x00007fff98bd7420 abort + 129
3 com.apple.Flexo 0x0000000109bdfd44 FFApplicationHandleExceptionThatShouldNotBeIgnored + 452
4 com.apple.CoreFoundation 0x00007fff836f4d5a __handleUncaughtException + 746
5 libobjc.A.dylib 0x00007fff98261f15 _objc_terminate() + 94
6 libc++abi.dylib 0x00007fff97754d69 std::__terminate(void (*)()) + 8
7 libc++abi.dylib 0x00007fff97754de3 std::terminate() + 51
8 libdispatch.dylib 0x00007fff98b0d0cc _dispatch_client_callout + 28
9 libdispatch.dylib 0x00007fff98b1c2c4 _dispatch_queue_override_invoke + 837
10 libdispatch.dylib 0x00007fff98b0ee70 _dispatch_root_queue_drain + 476
11 libdispatch.dylib 0x00007fff98b0ec47 _dispatch_worker_thread3 + 99
12 libsystem_pthread.dylib 0x00007fff98d5a712 _pthread_wqthread + 1299
13 libsystem_pthread.dylib 0x00007fff98d5a1ed start_wqthread + 13

Thanks again for your help! :)

Please Log in or Create an account to join the conversation.

[CRASH] FCPX Import Error 25 Jan 2017 23:03 #85190

  • joema
  • joema's Avatar
  • Offline
  • Platinum Boarder
  • Platinum Boarder
  • Posts: 1558
  • Karma: 27
  • Thank you received: 334
Your 2nd stack trace is identical to mine. This does not always indicate the same problem but in this case I think it does because the steps to reproduce it are the same.

This is what happens when Apple does not pursue the root problem. Of course erasing the boot drive and reinstalling macOS plus every app, utility and plugin will at least temporarily resolve the momentary problem and it gets the support guys off the hook -- temporarily. But it leaves us exposed to things like this.

I accept they can't analytically pursue every odd behavior because it's very time consuming and requires a high level of expertise. Typically only 1 in 100 support engineers have the training, experience and source code access, so that's a precious commodity. However IMO it should have been expended in this case.

Your current options are limited -- go back to 10.2.3 or erase your boot drive and reinstall macOS, FCPX and every single app, utility and plugin.

The fastest way to help Apple resolve cases like this is isolating a small, portable replication scenario. Unfortunately that's not always possible, especially where (a) it's an interaction between the OS and app, or (b) Where there is limited troubleshooting support in the app. E.g, I don't think FCPX has a "safe mode" which disables all plugins, preferences, etc.

There is a macOS safe mode, invoked by booting while holding the Shift key. In my case this did not prevent the problem.

While pruning the scenario to simplify it, this will sometimes determine the problem boundaries and provide a workaround.

Please Log in or Create an account to join the conversation.

Last edit: by joema.

[CRASH] FCPX Import Error 25 Jan 2017 23:22 #85192

  • joema
  • joema's Avatar
  • Offline
  • Platinum Boarder
  • Platinum Boarder
  • Posts: 1558
  • Karma: 27
  • Thank you received: 334
agam.yunus, could you please state what Mac hardware you are using? I don't think it's hardware related, but we must consider all possibilities. In my case the problem still happened on my 2015 top-spec iMac 27 with all external devices unplugged, network unplugged, and the media on the boot drive.

Edit/add: please include your exact CPU, RAM speed in Ghz. I see several people on TonyMacx86.com have encountered this, and all but one are running a 4Ghz i7-6700K; the other one is on an i5-3570K, probably overclocked to at least 4Ghz.

I just booted off my old Carbon Copy backup which will reproduce the problem if restored to the iMac SSD boot drive, and it did not happen. The backup drive is a 2-drive Thunderbolt RAID-0 array but it's a lot slower than the internal SSD. This could be a race condition involving multi-thread synchronization that only happens under specific timing.

Please Log in or Create an account to join the conversation.

Last edit: by joema.

[CRASH] FCPX Import Error 26 Jan 2017 04:54 #85201

  • agam.yunus
  • agam.yunus's Avatar Topic Author
  • Offline
  • Fresh Boarder
  • Fresh Boarder
  • Posts: 10
  • Thank you received: 0
Hi @joema

I'm using a customac with below specs.

CPU: Intel i7 6700 Skylake 4GHz
RAM: 32GB RAM 2133Mhz
MOBO: Gigabyte Z-170-X UD5 TH
GPU: Radeon RX480 8GB (Metal & Rotation supported)
SSD: 500GB m.2

I have a friend who have the same specs running FCPX 10.3.x without any problem. Appreciate your help and inputs :)

Please Log in or Create an account to join the conversation.

[CRASH] FCPX 10.3 Import Error 26 Jan 2017 10:41 #85202

  • cdw1960
  • cdw1960's Avatar
  • Offline
  • Junior Boarder
  • Junior Boarder
  • Posts: 29
  • Thank you received: 2
Why did I have at the back of my mind - 'I bet he's using an Hackintosh' :ohmy:

The Hackintosh is the problem not FCPX.

Please Log in or Create an account to join the conversation.

[CRASH] FCPX 10.3 Import Error 26 Jan 2017 13:10 #85211

  • joema
  • joema's Avatar
  • Offline
  • Platinum Boarder
  • Platinum Boarder
  • Posts: 1558
  • Karma: 27
  • Thank you received: 334

cdw1960 wrote: ...The Hackintosh is the problem not FCPX.


The Hackintosh has nothing to do with this problem -- I had the same problem on a stock 2015 iMac 27. It even had Apple RAM. I just verified I can still reproduce the problem -- on my iMac 27 -- using a Time Machine backup.

However most of the currently-identifiable problem reports are from the Hackintosh community. This is possibly due to "sampling bias" because (1) They are running faster machines hence more likely to encounter the problem if this is a multi-thread race condition, and (2) They are generally more technically astute, hence more likely to report the problem using terminology that allows finding that report via a Google search.

It's likely a lot of other FCPX users on stock 4Ghz iMacs are encountering this but have not reported it using specific terminology.

Please Log in or Create an account to join the conversation.

[CRASH] FCPX 10.3 Import Error 26 Jan 2017 14:51 #85214

  • cdw1960
  • cdw1960's Avatar
  • Offline
  • Junior Boarder
  • Junior Boarder
  • Posts: 29
  • Thank you received: 2

The Hackintosh has nothing to do with this problem -- I had the same problem on a stock 2015 iMac 27. It even had Apple RAM. I just verified I can still reproduce the problem -- on my iMac 27 -- using a Time Machine backup.


I take your point. I just thought it odd that he didn't mention that it was an Hackintosh right at the start...

It's likely a lot of other FCPX users on stock 4Ghz iMacs are encountering this but have not reported it using specific terminology.


'Its likely'; don't you just love those two words posing as 'facts'! I have a late 2015 iMac with no such problems. Am I just lucky?

Perhaps the original commentator could try and get his hands a real Mac and see if he can replicate the problem, this would, probably, make a difference. Who knows... :whistle:

Please Log in or Create an account to join the conversation.

[CRASH] FCPX Import Error 26 Jan 2017 15:02 #85216

  • joema
  • joema's Avatar
  • Offline
  • Platinum Boarder
  • Platinum Boarder
  • Posts: 1558
  • Karma: 27
  • Thank you received: 334

agam.yunus wrote: ...I have a friend who have the same specs running FCPX 10.3.x without any problem. Appreciate your help and inputs :)


I just determined that on my iMac 27 it's related to having an .M4A audio file in the import folder. Not any specific .M4A file -- apparently any one will cause it. This file was a downloaded Podcast from iTunes which was in the default FCPX import folder. However testing on my 2015 MBP does not show the problem, so it may be a combination of file and a race condition which only happens on fast machines.

Even though it crashes before I select any file, it is still enumerating the files in the import folder and doing some kind of processing. Something about that is going wrong. It might be reading a file header and dereferencing a pointer without validating it and maybe there's something out of spec in the header.

Can you please check what items are in your import folder -- whether there are any .M4A files. Either way, change the import folder to somewhere else with no files in it, and try that. If it doesn't crash, then move in several files at a time from your original import folder and see if one of those is causing it.

Please Log in or Create an account to join the conversation.

[CRASH] FCPX Import Error 26 Jan 2017 15:45 #85220

  • agam.yunus
  • agam.yunus's Avatar Topic Author
  • Offline
  • Fresh Boarder
  • Fresh Boarder
  • Posts: 10
  • Thank you received: 0
Hi @joema,

Thanks again. I tried creating a new folder in a new external, copied .MP4 and a couple of .MOV files (ProRes 444, 422, LT, Proxy) separately and tried importing each one of them without a success.

I pressed down cmd+opt and click FCPX apps to delete all preference and create new library for each attempt to import the files.

Please Log in or Create an account to join the conversation.

[CRASH] FCPX Import Error 26 Jan 2017 16:44 #85226

  • joema
  • joema's Avatar
  • Offline
  • Platinum Boarder
  • Platinum Boarder
  • Posts: 1558
  • Karma: 27
  • Thank you received: 334
So it's happening with a fresh import folder where the only items are an .MP4 and two .MOV files? I assume those are on your internal SSD drive.

Can you try putting those on a slower drive like a USB thumb drive or portable USB hard drive and try that? In my testing it is sensitive to both CPU speed and hard drive speed. It may not be the .M4A file itself that causes it, rather it (in conjunction with other factors) exposes a multithreaded timing window that causes the crash.

Can you try reducing your CPU clock speed to say 3 or 3.5Ghz and try again? Just trying to determine how sensitive it is to timing.

Please Log in or Create an account to join the conversation.

[CRASH] FCPX Import Error 26 Jan 2017 16:50 #85228

  • agam.yunus
  • agam.yunus's Avatar Topic Author
  • Offline
  • Fresh Boarder
  • Fresh Boarder
  • Posts: 10
  • Thank you received: 0
Nope, I tried copying 1 file after each other to test if the problem if the format of the files. I put these files in an internal SATA drive. The previous attempt was importing from a USB 3.0 external drive. Sure, I will try reducing the CPU clock speed. As always, thanks for your help! :cheer:

Please Log in or Create an account to join the conversation.

  • Page:
  • 1
  • 2