fbpx
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.

FCPx crashes when I close Library

More
12 Aug 2023 11:49 #126760 by FinalCutdown
I am almost finishing my documentary but now every time I try to close my library FCPx crashes.
When I reopen it, the Library is open again.
What can I do?

Translated Report (Full Report Below)
Process:               Final Cut Pro [1810]Path:                  /Applications/Final Cut Pro.app/Contents/MacOS/Final Cut ProIdentifier:            com.apple.FinalCutVersion:               10.6.6 (406338)Build Info:            ProEditor-40600338016000000~4 (19A341a)App Item ID:           424389933App External ID:       856984246Code Type:             ARM-64 (Native)Parent Process:        launchd [1]User ID:               501Date/Time:             2023-08-12 13:46:22.2438 +0200OS Version:            macOS 13.4.1 (22F770820d)Report Version:        12Anonymous UUID:        AC8E34B5-8D1E-CFAB-BC26-6B651D72BA49Sleep/Wake UUID:       D3A51FED-1716-4F9B-B2D2-1EE17E08AB33Time Awake Since Boot: 20000 secondsTime Since Wake:       4483 secondsSystem Integrity Protection: enabledCrashed Thread:        47  Dispatch queue: FFLibraryFilesControllerException Type:        EXC_BAD_ACCESS (SIGSEGV)Exception Codes:       KERN_INVALID_ADDRESS at 0x000092e20a31ce10 -> 0x000012e20a31ce10 (possible pointer authentication failure)Exception Codes:       0x0000000000000001, 0x000092e20a31ce10Termination Reason:    Namespace SIGNAL, Code 11 Segmentation fault: 11Terminating Process:   exc handler [1810]VM Region Info: 0x12e20a31ce10 is not in any region.  Bytes after previous region: 20281006607889  Bytes before following region: 84791073321456      REGION TYPE                    START - END         [ VSIZE] PRT/MAX SHRMOD  REGION DETAIL      commpage (reserved)        1000000000-7000000000   [384.0G] ---/--- SM=NUL  ...(unallocated)--->  GAP OF 0x5f9000000000 BYTES      MALLOC_NANO              600000000000-600008000000 [128.0M] rw-/rwx SM=PRV  Thread 0::  Dispatch queue: com.apple.main-thread0   libsystem_kernel.dylib               0x188047f14 mach_msg2_trap + 81   libsystem_kernel.dylib               0x18805a240 mach_msg2_internal + 802   libsystem_kernel.dylib               0x188050b78 mach_msg_overwrite + 6043   libsystem_kernel.dylib               0x188048290 mach_msg + 244   CoreFoundation                       0x1881667e4 __CFRunLoopServiceMachPort + 1605   CoreFoundation                       0x1881650c4 __CFRunLoopRun + 12086   CoreFoundation                       0x1881644b8 CFRunLoopRunSpecific + 6127   HIToolbox                            0x1919aec40 RunCurrentEventLoopInMode + 2928   HIToolbox                            0x1919aea7c ReceiveNextEventCommon + 6489   HIToolbox                            0x1919ae7d4 _BlockUntilNextEventMatchingListInModeWithFilter + 7610  AppKit                               0x18b385d44 _DPSNextEvent + 63611  AppKit                               0x18b384ee0 -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 71612  AppKit                               0x18b379344 -[NSApplication run] + 46413  LunaKit                              0x103232f38 LKApplicationMain + 20414  dyld                                 0x187d2ff28 start + 2236

Please Log in to join the conversation.

More
12 Aug 2023 12:32 #126761 by Tom Wolsky
Trash the settings. Hold Opt-Cmd as you launch the application.

Please Log in to join the conversation.

More
12 Aug 2023 12:35 #126762 by FinalCutdown
Thanks for your help! For now just closing and opening did the trick. I can now close the library and FCP stays open.

Please Log in to join the conversation.

More
12 Aug 2023 16:17 #126765 by FinalCutdown
Okay, after restarting FCPx I could close the library exactly ONE time. The second time it crashed again. I deleted all render files and copied everything over to a new library and it works again.

I am quite sure that the problem was, that I had to mess around with the timecode of my source clip and this created problems with linked proxies..
fcp.co/forum/4-final-cut-pro-x-fcpx/3632...ecode-from-sony-a7s3

So beware... Sony timecode and FCPx is a real mess..

Please Log in to join the conversation.