- Posts: 5
- Thank you received: 0
3 Post Moderation Rule for New Boarders (25 Jan 2021)
New boarders will have their posts moderated - Don't worry if you cannot see your post immediately.
"Final Cut Pro Quit Unexpectedly"
02 Sep 2014 10:04 #52066
by FCPN00b
"Final Cut Pro Quit Unexpectedly" was created by FCPN00b
G'day.
I have FCPX and after I did an update I have been unable to open any of my libraries, and if I try to create a new library I get the same error:
"final cut pro quit unexpectedly"
I have tried trashing preferences, repair disk permissions. Uninstalled FCPX, reinstalled etc, but the problem persists.
I also disconnected my external HDs with the libraries, FCPX then prompted me to create a new one, but still the same problem.
Any ideas ?
Thanks.
I have FCPX and after I did an update I have been unable to open any of my libraries, and if I try to create a new library I get the same error:
"final cut pro quit unexpectedly"
I have tried trashing preferences, repair disk permissions. Uninstalled FCPX, reinstalled etc, but the problem persists.
I also disconnected my external HDs with the libraries, FCPX then prompted me to create a new one, but still the same problem.
Any ideas ?
Thanks.
Please Log in to join the conversation.
- ronny courtens
-
- Offline
- Moderator
-
Less
More
- Posts: 4455
- Thank you received: 962
02 Sep 2014 12:20 #52075
by ronny courtens
Replied by ronny courtens on topic "Final Cut Pro Quit Unexpectedly"
Hi Mike, welcome to the forum.
- What is the version of FCP X you are running?
- What computer are you working on?
- How much RAM do you have?
-Ronny
- What is the version of FCP X you are running?
- What computer are you working on?
- How much RAM do you have?
-Ronny
Please Log in to join the conversation.
02 Sep 2014 12:31 #52076
by FCPN00b
Replied by FCPN00b on topic "Final Cut Pro Quit Unexpectedly"
Thanks Ronny, I wish I had found it sooner.
FCP 10.1.3
This is what I can tell you about my Mac:
Hardware Overview:
Model Name: MacBook Pro
Model Identifier: MacBookPro10,1
Processor Name: Intel Core i7
Processor Speed: 2.8 GHz
Number of Processors: 1
Total Number of Cores: 4
L2 Cache (per Core): 256 KB
L3 Cache: 8 MB
Memory: 16 GB
Boot ROM Version: MBP101.00EE.B03
SMC Version (system): 2.3f36
This what I can tell you about the crash:
Process: Final Cut Pro [3166]
Path: /Applications/Final Cut Pro.app/Contents/MacOS/Final Cut Pro
Identifier: com.apple.FinalCut
Version: 10.1.3 (251130)
Build Info: ProEditor-25113000038000000~1
App Item ID: 424389933
App External ID: 668174963
Code Type: X86-64 (Native)
Parent Process: launchd [205]
Responsible: Final Cut Pro [3166]
User ID: 502
Date/Time: 2014-09-02 22:28:06.904 +1000
OS Version: Mac OS X 10.9.4 (13E28)
Report Version: 11
Anonymous UUID: 21FBA26A-6447-6B56-CC66-7873B66EE0CC
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Application Specific Information:
*** -[NSFileManager moveItemAtURL:toURL:error:]: source URL is nil
abort() called
FCP 10.1.3
This is what I can tell you about my Mac:
Hardware Overview:
Model Name: MacBook Pro
Model Identifier: MacBookPro10,1
Processor Name: Intel Core i7
Processor Speed: 2.8 GHz
Number of Processors: 1
Total Number of Cores: 4
L2 Cache (per Core): 256 KB
L3 Cache: 8 MB
Memory: 16 GB
Boot ROM Version: MBP101.00EE.B03
SMC Version (system): 2.3f36
This what I can tell you about the crash:
Process: Final Cut Pro [3166]
Path: /Applications/Final Cut Pro.app/Contents/MacOS/Final Cut Pro
Identifier: com.apple.FinalCut
Version: 10.1.3 (251130)
Build Info: ProEditor-25113000038000000~1
App Item ID: 424389933
App External ID: 668174963
Code Type: X86-64 (Native)
Parent Process: launchd [205]
Responsible: Final Cut Pro [3166]
User ID: 502
Date/Time: 2014-09-02 22:28:06.904 +1000
OS Version: Mac OS X 10.9.4 (13E28)
Report Version: 11
Anonymous UUID: 21FBA26A-6447-6B56-CC66-7873B66EE0CC
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Application Specific Information:
*** -[NSFileManager moveItemAtURL:toURL:error:]: source URL is nil
abort() called
Please Log in to join the conversation.
- ronny courtens
-
- Offline
- Moderator
-
Less
More
- Posts: 4455
- Thank you received: 962
02 Sep 2014 12:49 #52078
by ronny courtens
Replied by ronny courtens on topic "Final Cut Pro Quit Unexpectedly"
Thank you for the detailed information. I assume you are running the latest version of Mavericks and certainly NOT a Yosemite beta? If so:
Disconnect your internet or wi fi connection and also disconnect any external drives. Launch FCP X while holding the ALT and the CMD keys pressed. You will get a message about deleting your preferences, just click Delete Preferences and let FCP X open.
Create a new Library on your system drive and press Save. Does FCP X crash again?
If it does, use this utility to completely remove FCP X from your system: www.digitalrebellion.com/fcsremover/
Then reconnect your internet/wi fi connection and reinstall FCP X from the App store. Finally try opening FCP X again.
- Ronny
Disconnect your internet or wi fi connection and also disconnect any external drives. Launch FCP X while holding the ALT and the CMD keys pressed. You will get a message about deleting your preferences, just click Delete Preferences and let FCP X open.
Create a new Library on your system drive and press Save. Does FCP X crash again?
If it does, use this utility to completely remove FCP X from your system: www.digitalrebellion.com/fcsremover/
Then reconnect your internet/wi fi connection and reinstall FCP X from the App store. Finally try opening FCP X again.
- Ronny
Please Log in to join the conversation.
02 Sep 2014 13:02 #52079
by FCPN00b
Replied by FCPN00b on topic "Final Cut Pro Quit Unexpectedly"
I will try thanks
Please Log in to join the conversation.
03 Sep 2014 05:48 #52125
by FCPN00b
Replied by FCPN00b on topic "Final Cut Pro Quit Unexpectedly"
G'day Ronny,
I did exactly as you instructed, unfortunately the same error persists
Mike
I did exactly as you instructed, unfortunately the same error persists
Mike
Please Log in to join the conversation.
- ronny courtens
-
- Offline
- Moderator
-
Less
More
- Posts: 4455
- Thank you received: 962
03 Sep 2014 07:01 - 03 Sep 2014 07:02 #52127
by ronny courtens
Replied by ronny courtens on topic "Final Cut Pro Quit Unexpectedly"
Hey Mike,
Sorry to hear that.
The crash report you have posted actually surprises me. The crashes are caused by NSFileManager and the error code you get means that the application crashes when trying to move an object from one directory to another (moveItemAtURL:toURL:error) and it cannot find the source file (source URL is nil).
You say this started "after I did an update". Was this an update for FCP X or for something else?
- Ronny
Sorry to hear that.
The crash report you have posted actually surprises me. The crashes are caused by NSFileManager and the error code you get means that the application crashes when trying to move an object from one directory to another (moveItemAtURL:toURL:error) and it cannot find the source file (source URL is nil).
You say this started "after I did an update". Was this an update for FCP X or for something else?
- Ronny
Last edit: 03 Sep 2014 07:02 by ronny courtens.
Please Log in to join the conversation.
05 Sep 2014 22:52 #52241
by FCPN00b
Replied by FCPN00b on topic "Final Cut Pro Quit Unexpectedly"
Hi Ronny,
I appreciate your help.
I did an update through the App Store at some point on FCP, after which these problems began happening.
I also tried moving the libraries from my external hard drive to my internal hard drive to see if that helps, and I've move them back again. I've also completely disconnected the library hard drives and tried creating a new library, all of which fails.
Cheers,
Mike
I appreciate your help.
I did an update through the App Store at some point on FCP, after which these problems began happening.
I also tried moving the libraries from my external hard drive to my internal hard drive to see if that helps, and I've move them back again. I've also completely disconnected the library hard drives and tried creating a new library, all of which fails.
Cheers,
Mike
Please Log in to join the conversation.

