[CRASH] FCPX 10.3 Import Error

I am discussing this with Apple Tier 2 Pro Apps support and have offered to FedEx them a portable replication scenario on a USB drive.

Apple Pro Apps support said they'd get back to me sometime next week.

Hello,

I'm just reporting the same problem.
Hackintosh, macOS 10.11.5.

fdnt wrote: Hello,

I'm just reporting the same problem.
Hackintosh, macOS 10.11.5.

Can you please state your system specs? What CPU, what speed, etc. Also inspect whether you have an .M4A audio file in your import folder, or whether switching to a new import folder with just a few files is a workaround?

The current status is Apple said they don't need my portable replication scenario on a thumb drive. I assume this means the developers have a firm grasp on the problem and are confident they can fix it. I don't know what the timeframe is, but I would hope in the next maintenance update.

Hi Joema,

Again, thanks for your help . Sorry for my late reply, bit busy in the past weeks.

I've got this reply couple days ago from tonymac's forum about another solution that might probably work forApple computers as well.

I have a solution! I removed all everything beginning with IppleIntelSKLGraphics in the S/L/E folder. I was also sure to remove any boot flags retaining to graphics. Darkboot and sleep issues persist but is a small price to pay. FCPX 10.3 works flawlessly with full acceleration. BruceX taking ~35 seconds with 2GB Saffire RX 460.

I think he means go to system/library/extension and delete AppleIntelSKLGraphics.kext.

I haven't tried this method yet, since I still need my computer for my projects. Can't afford having crashes or any errors at the moment

MB : Gigabyte GA-Z97X-UD3H
GPU: SAPPHIRE AMD R9 280X TRI-X OC
CPU : i7 4790K
RAM : Crucial Ballistix Tactical 16GB
macOS on Samsung 850 EVO 500


I tried to convert libraries, to import folders, every kind of files, to drag and drop, etc.
Everything is working fine with FCP 10.12.3.

I had the same symptoms (crash as soon as the import dialogue was selected) but eventually traced this to a single corrupt video file in the directory from which I was trying to import. It does seem odd that the import procedure is not a little more robust. I finally noticed the corrupt file not through trial and error but because the OS wasn't giving it an icon in the Finder.

james.whitby wrote: I had the same symptoms (crash as soon as the import dialogue was selected) but eventually traced this to a single corrupt video file in the directory from which I was trying to import. It does seem odd that the import procedure is not a little more robust. I finally noticed the corrupt file not through trial and error but because the OS wasn't giving it an icon in the Finder.

In my case it was probably not a corrupt file, since it was an iTunes .M4A audio file which worked OK in various players. However for anyone experiencing immediate crashes on import, it makes sense to check for this possibility by pointing the import dialog to an empty folder and then putting a single "known good" file in it.

Ideally any import code should check for obvious file corruption, but this cannot always be determined. Video files usually don't have a CRC checksum. OTOH if the import code reads a header field from the media file, it should usually validate that before dereferencing it as a pointer or otherwise using it.

Unfortunately it's not always possible to know what are valid and invalid values. Even if this is knowable based on some spec, the vast majority of time the values will be within range. So from a programming standpoint it's a lot of work (and often slows runtime performance) to add validation checks for rare cases. It also can degrade reliability if the check itself is erroneous or based on some ambiguous spec, which then throws spurious errors when the file is really OK.

But I think in this case there is some deficiency in the FCPX import code which is being triggered by some file characteristic, whether that is corruption or not.

For me the perfect fix was to disable integrated graphics in BIOS settings. Now FCP works like a charm.

Reporting same problem. Apple is just not going to fix the issue as it is probably related to a kext or something that us pro users have installed. Who knows what it could be. If everyone reported it, maybe they would fix it, but I doubt they would be willing to help us hackintoshers.

MB : Gigabyte GA-Z170-UD5 TH
GPU: XFX RX 480
CPU : i7 6700
RAM : Crucial Ballistix Tactical 16GB
macOS on Samsung 850 EVO 250

JosephHolder wrote: Reporting same problem....probably related to a kext or something that us pro users have installed....I doubt they would be willing to help us hackintoshers.

It's definitely not always caused by a Hackintosh, as I experienced this on a stock 2015 iMac 27. Mine was caused by having a certain iTunes .M4A audio file in the import folder. Since the import dialog remembers the last folder location, every subsequent import attempt would crash upon launching the dialog. In my case the solution was to remove that file.

Hackintosh users have reported disabling integrated graphics on the motherboard BIOS prevented the problem. Unfortunately this also probably disables Quick Sync, so there's a performance loss during H264 encode/decode.

There may be multiple code paths and conditions which cause the crash during import. Without seeing the stack trace of the crashing thread it's hard to tell them apart, and even that is not definitive.

So I've got mine working, seeing as I had to encode a project. H.264 seems a little slow, but I think it's fine.

I didn't disable My internal Intel i7 graphics. I just had to start up with the RX480 being seen as the main card. The way rx480s work (on a mac) , you cannot boot without the integrate graphics on, however if I have a monitor plugged into my 480 it boots properly.

Since you are on an actual mac, I would suggest disabling your integrated graphics to see what it does. There is a setting in system preferences under energy saver that might do it, alternatively you could try that app called GFXstatus

JosephHolder wrote: ...Since you are on an actual mac, I would suggest disabling your integrated graphics to see what it does. There is a setting in system preferences under energy saver that might do it, alternatively you could try that app called GFXstatus

Disabling the integrated GPU is not possible on an iMac, whether by energy saver or gfxCardStatus.

Hi guys...
After freaking out and tried every single possibility to fix this I realised that the problem was that FCPX has problems to handle and render .m4u files to preview of show this files on import window, was a shame because its a tipe of file that Apple devices creates.

So, I finally solve changing the extension of the .m4u files on the folders to .mp3.
Works so fine. I tested many times surfing in folders with those files changed to .mp3. But once I open one folder with an .m4u file... #crash

I couldn't surrender to format and reinstall everything from 0.

Hope this help you guys.