Apple Event: May 7th at 7 am PT

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Level 1

4 points

Motion 5.0.5 Crashes Upon Launch

Hey Everyone,

I updated to Motion 5.0.5 and it crashed the first, and every time after, right at launch. I have since trashed the preferences(using Preference Manager) and deleted the app and reinstalled from App Store twice, still with the same results.

Anyone have an idea of what to do?

Thanks,

Richard

Here is the beginning of the Problem Report. I don't know if that helps.

Process: Motion [8048]

Path: /Applications/Motion.app/Contents/MacOS/Motion

Identifier: com.apple.motionapp

Version: 5.0.5 (210813)

Build Info: Motion-21081003010000000~1

App Item ID: 434290957

App External ID: 10982841

Code Type: X86-64 (Native)

Parent Process: launchd [149]

User ID: 501

Date/Time: 2012-11-03 00:28:14.399 -0700

OS Version: Mac OS X 10.8.2 (12C60)

Report Version: 10

Interval Since Last Report: 73971 sec

Crashes Since Last Report: 4

Per-App Interval Since Last Report: 61 sec

Per-App Crashes Since Last Report: 4

Anonymous UUID: A39A209E-6A66-28A4-3AD7-C2339C29DDC6

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Type: EXC_BAD_ACCESS (SIGSEGV)

Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000

VM Regions Near 0:

-->

__TEXT 0000000100000000-0000000100007000 [ 28K] r-x/rwx SM=COW /Applications/Motion.app/Contents/MacOS/Motion

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread

0 com.apple.CoreFoundation 0x00007fff910a82ea CFURLCopyPath + 10

1 com.apple.procore.framework 0x00000001006d65c5 PCXMLReadStream::PCXMLReadStream(PCURL const&) + 87

2 com.apple.ozone.framework 0x0000000100b3f9e8 -[OZFileSystemLibEntry readXMLData] + 168

3 com.apple.ozone.framework 0x0000000100b3af25 -[OZFileSystemLibEntry readDirectoryContents:] + 1845

4 com.apple.ozone.framework 0x0000000100b3c279 -[OZFileSystemLibEntry forceReadOfContents:] + 57

5 com.apple.ozone.framework 0x0000000100b3c2dd -[OZFileSystemLibEntry forceReadOfContents:] + 157

6 com.apple.ozone.framework 0x0000000100c60e9f -[OZLibraryModule buildTreeForMotion] + 815

7 com.apple.ozone.framework 0x00000001008ed70b +[OZApplicationController sharedLibraryModule] + 107

8 com.apple.ozone.framework 0x00000001008ed42b -[OZApplicationController applicationDidFinishLaunching:] + 571

9 com.apple.CoreFoundation 0x00007fff910c847a _CFXNotificationPost + 2554

10 com.apple.Foundation 0x00007fff91ade846 -[NSNotificationCenter postNotificationName:object:userInfo:] + 64

11 com.apple.AppKit 0x00007fff8f9e660d -[NSApplication _postDidFinishNotification] + 292

12 com.apple.AppKit 0x00007fff8f9e6346 -[NSApplication _sendFinishLaunchingNotification] + 216

13 com.apple.AppKit 0x00007fff8f9e3532 -[NSApplication(NSAppleEventHandling) _handleAEOpenEvent:] + 566

14 com.apple.AppKit 0x00007fff8f9e312c -[NSApplication(NSAppleEventHandling) _handleCoreEvent:withReplyEvent:] + 351

15 com.apple.Foundation 0x00007fff91af812b -[NSAppleEventManager dispatchRawAppleEvent:withRawReply:handlerRefCon:] + 308

16 com.apple.Foundation 0x00007fff91af7f8d _NSAppleEventManagerGenericHandler + 106

17 com.apple.AE 0x00007fff94bb8b48 aeDispatchAppleEvent(AEDesc const*, AEDesc*, unsigned int, unsigned char*) + 307

18 com.apple.AE 0x00007fff94bb89a9 dispatchEventAndSendReply(AEDesc const*, AEDesc*) + 37

19 com.apple.AE 0x00007fff94bb8869 aeProcessAppleEvent + 318

20 com.apple.HIToolbox 0x00007fff8d5328e9 AEProcessAppleEvent + 100

21 com.apple.AppKit 0x00007fff8f9df916 _DPSNextEvent + 1456

22 com.apple.AppKit 0x00007fff8f9deed2 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 128

23 com.apple.AppKit 0x00007fff8f9d6283 -[NSApplication run] + 517

24 com.apple.prokit 0x00000001000e0324 NSProApplicationMain + 378

25 com.apple.motionapp 0x0000000100002b2b 0x100000000 + 11051

26 com.apple.motionapp 0x0000000100001a24 0x100000000 + 6692

Thread 1:: Dispatch queue: com.apple.libdispatch-manager

0 libsystem_kernel.dylib 0x00007fff9417bd16 kevent + 10

1 libdispatch.dylib 0x00007fff952a5dea _dispatch_mgr_invoke + 883

2 libdispatch.dylib 0x00007fff952a59ee _dispatch_mgr_thread + 54

Thread 2:: com.apple.ProGL.object-deletion

0 libsystem_kernel.dylib 0x00007fff9417b0fa __psynch_cvwait + 10

1 libsystem_c.dylib 0x00007fff8ef35f89 _pthread_cond_wait + 869

2 com.apple.progl.framework 0x0000000103a2e779 (anonymous namespace)::threadFunc(void*) + 71

3 com.apple.procore.framework 0x00000001006db63f PCThread::startup(void*) + 29

4 libsystem_c.dylib 0x00007fff8ef31742 _pthread_start + 327

5 libsystem_c.dylib 0x00007fff8ef1e181 thread_start + 13

Thread 3:: com.apple.flexo.throttled-scheduled-io

0 libsystem_kernel.dylib 0x00007fff9417b0fa __psynch_cvwait + 10

1 libsystem_c.dylib 0x00007fff8ef35f89 _pthread_cond_wait + 869

2 com.apple.Flexo 0x0000000101926da3 Synchronizable::Wait() + 51

3 com.apple.Flexo 0x00000001017ab644 ThrottleReadImpl::Run() + 196

4 com.apple.Flexo 0x000000010192d4ff Thread::RunHelper(void*) + 47

5 libsystem_c.dylib 0x00007fff8ef31742 _pthread_start + 327

6 libsystem_c.dylib 0x00007fff8ef1e181 thread_start + 13

Thread 4:: com.apple.flexo.appthrottled-scheduled-io

0 libsystem_kernel.dylib 0x00007fff9417b0fa __psynch_cvwait + 10

1 libsystem_c.dylib 0x00007fff8ef35f89 _pthread_cond_wait + 869

2 com.apple.Flexo 0x0000000101926da3 Synchronizable::Wait() + 51

3 com.apple.Flexo 0x00000001017ab644 ThrottleReadImpl::Run() + 196

4 com.apple.Flexo 0x000000010192d4ff Thread::RunHelper(void*) + 47

5 libsystem_c.dylib 0x00007fff8ef31742 _pthread_start + 327

6 libsystem_c.dylib 0x00007fff8ef1e181 thread_start + 13

Thread 5:

0 libsystem_kernel.dylib 0x00007fff9417b6d6 __workq_kernreturn + 10

1 libsystem_c.dylib 0x00007fff8ef33eec _pthread_workq_return + 25

2 libsystem_c.dylib 0x00007fff8ef33cb3 _pthread_wqthread + 412

3 libsystem_c.dylib 0x00007fff8ef1e171 start_wqthread + 13

Thread 6:

0 libsystem_kernel.dylib 0x00007fff9417b6d6 __workq_kernreturn + 10

1 libsystem_c.dylib 0x00007fff8ef33eec _pthread_workq_return + 25

2 libsystem_c.dylib 0x00007fff8ef33cb3 _pthread_wqthread + 412

3 libsystem_c.dylib 0x00007fff8ef1e171 start_wqthread + 13

Thread 7:

0 libsystem_kernel.dylib 0x00007fff9417b6d6 __workq_kernreturn + 10

1 libsystem_c.dylib 0x00007fff8ef33eec _pthread_workq_return + 25

2 libsystem_c.dylib 0x00007fff8ef33cb3 _pthread_wqthread + 412

3 libsystem_c.dylib 0x00007fff8ef1e171 start_wqthread + 13

Thread 8:

0 libsystem_kernel.dylib 0x00007fff9417b6d6 __workq_kernreturn + 10

1 libsystem_c.dylib 0x00007fff8ef33eec _pthread_workq_return + 25

2 libsystem_c.dylib 0x00007fff8ef33cb3 _pthread_wqthread + 412

3 libsystem_c.dylib 0x00007fff8ef1e171 start_wqthread + 13

Thread 9:: QTKit: listenOnDelegatePort

0 libsystem_kernel.dylib 0x00007fff94179686 mach_msg_trap + 10

1 libsystem_kernel.dylib 0x00007fff94178c42 mach_msg + 70

2 com.apple.CoreFoundation 0x00007fff910b2803 __CFRunLoopServiceMachPort + 195

3 com.apple.CoreFoundation 0x00007fff910b7ee6 __CFRunLoopRun + 1078

4 com.apple.CoreFoundation 0x00007fff910b76b2 CFRunLoopRunSpecific + 290

5 com.apple.CoreFoundation 0x00007fff910c6371 CFRunLoopRun + 97

6 com.apple.QTKit 0x00007fff90873496 listenOnDelegatePort + 403

7 libsystem_c.dylib 0x00007fff8ef31742 _pthread_start + 327

8 libsystem_c.dylib 0x00007fff8ef1e181 thread_start + 13

Thread 10:: QTKit: listenOnNotificationPort

0 libsystem_kernel.dylib 0x00007fff94179686 mach_msg_trap + 10

1 libsystem_kernel.dylib 0x00007fff94178c42 mach_msg + 70

2 com.apple.CoreFoundation 0x00007fff910b2803 __CFRunLoopServiceMachPort + 195

3 com.apple.CoreFoundation 0x00007fff910b7ee6 __CFRunLoopRun + 1078

4 com.apple.CoreFoundation 0x00007fff910b76b2 CFRunLoopRunSpecific + 290

5 com.apple.CoreFoundation 0x00007fff910c6371 CFRunLoopRun + 97

6 com.apple.QTKit 0x00007fff90873931 listenOnNotificationPort + 371

7 libsystem_c.dylib 0x00007fff8ef31742 _pthread_start + 327

8 libsystem_c.dylib 0x00007fff8ef1e181 thread_start + 13

Thread 11:: QTKit: QTCALayerRendererPendingQWorkLoop

0 libsystem_kernel.dylib 0x00007fff94179686 mach_msg_trap + 10

1 libsystem_kernel.dylib 0x00007fff94178c42 mach_msg + 70

2 com.apple.CoreFoundation 0x00007fff910b2803 __CFRunLoopServiceMachPort + 195

3 com.apple.CoreFoundation 0x00007fff910b7ee6 __CFRunLoopRun + 1078

4 com.apple.CoreFoundation 0x00007fff910b76b2 CFRunLoopRunSpecific + 290

5 com.apple.CoreFoundation 0x00007fff910c6371 CFRunLoopRun + 97

6 com.apple.QTKit 0x00007fff908f55a4 QTCALayerRendererPendingQWorkLoop + 498

7 libsystem_c.dylib 0x00007fff8ef31742 _pthread_start + 327

8 libsystem_c.dylib 0x00007fff8ef1e181 thread_start + 13

Thread 12:: QTKit: QTMachPortImageProviderWorkLoop

0 libsystem_kernel.dylib 0x00007fff94179686 mach_msg_trap + 10

1 libsystem_kernel.dylib 0x00007fff94178c42 mach_msg + 70

2 com.apple.CoreFoundation 0x00007fff910b2803 __CFRunLoopServiceMachPort + 195

3 com.apple.CoreFoundation 0x00007fff910b7ee6 __CFRunLoopRun + 1078

4 com.apple.CoreFoundation 0x00007fff910b76b2 CFRunLoopRunSpecific + 290

5 com.apple.CoreFoundation 0x00007fff910c6371 CFRunLoopRun + 97

6 com.apple.QTKit 0x00007fff90934d73 QTMachPortImageProviderWorkLoop + 315

7 libsystem_c.dylib 0x00007fff8ef31742 _pthread_start + 327

8 libsystem_c.dylib 0x00007fff8ef1e181 thread_start + 13

Thread 13:: QTKit: QTMachPortImageProviderWorkLoop

0 libsystem_kernel.dylib 0x00007fff94179686 mach_msg_trap + 10

1 libsystem_kernel.dylib 0x00007fff94178c42 mach_msg + 70

2 com.apple.CoreFoundation 0x00007fff910b2803 __CFRunLoopServiceMachPort + 195

3 com.apple.CoreFoundation 0x00007fff910b7ee6 __CFRunLoopRun + 1078

4 com.apple.CoreFoundation 0x00007fff910b76b2 CFRunLoopRunSpecific + 290

5 com.apple.CoreFoundation 0x00007fff910c6371 CFRunLoopRun + 97

6 com.apple.QTKit 0x00007fff90934d73 QTMachPortImageProviderWorkLoop + 315

7 libsystem_c.dylib 0x00007fff8ef31742 _pthread_start + 327

8 libsystem_c.dylib 0x00007fff8ef1e181 thread_start + 13

Thread 14:: QTKit: QTMachPortImageProviderWorkLoop

0 libsystem_kernel.dylib 0x00007fff94179686 mach_msg_trap + 10

1 libsystem_kernel.dylib 0x00007fff94178c42 mach_msg + 70

2 com.apple.CoreFoundation 0x00007fff910b2803 __CFRunLoopServiceMachPort + 195

3 com.apple.CoreFoundation 0x00007fff910b7ee6 __CFRunLoopRun + 1078

4 com.apple.CoreFoundation 0x00007fff910b76b2 CFRunLoopRunSpecific + 290

5 com.apple.CoreFoundation 0x00007fff910c6371 CFRunLoopRun + 97

6 com.apple.QTKit 0x00007fff90934d73 QTMachPortImageProviderWorkLoop + 315

7 libsystem_c.dylib 0x00007fff8ef31742 _pthread_start + 327

8 libsystem_c.dylib 0x00007fff8ef1e181 thread_start + 13

Thread 15:: QTKit: QTMachPortImageProviderWorkLoop

0 libsystem_kernel.dylib 0x00007fff94179686 mach_msg_trap + 10

1 libsystem_kernel.dylib 0x00007fff94178c42 mach_msg + 70

2 com.apple.CoreFoundation 0x00007fff910b2803 __CFRunLoopServiceMachPort + 195

3 com.apple.CoreFoundation 0x00007fff910b7ee6 __CFRunLoopRun + 1078

4 com.apple.CoreFoundation 0x00007fff910b76b2 CFRunLoopRunSpecific + 290

5 com.apple.CoreFoundation 0x00007fff910c6371 CFRunLoopRun + 97

6 com.apple.QTKit 0x00007fff90934d73 QTMachPortImageProviderWorkLoop + 315

7 libsystem_c.dylib 0x00007fff8ef31742 _pthread_start + 327

8 libsystem_c.dylib 0x00007fff8ef1e181 thread_start + 13

Thread 0 crashed with X86 Thread State (64-bit):

rax: 0x00000001007b0720 rbx: 0x00007fff5fbfe4c8 rcx: 0x0000000000000001 rdx: 0x0000000000000001

rdi: 0x0000000000000000 rsi: 0x00007fff5fbfe4c8 rbp: 0x00007fff5fbfe370 rsp: 0x00007fff5fbfe370

r8: 0x0000000105080e00 r9: 0x000000000000001d r10: 0x0000000009000004 r11: 0x0000000020000000

r12: 0x0000000000000000 r13: 0x000000012acc17e0 r14: 0x00007fff5fbfe5b8 r15: 0x00007fff5fbfe4d0

rip: 0x00007fff910a82ea rfl: 0x0000000000010246 cr2: 0x0000000000000000

Logical CPU: 2

Mac Pro, Mac OS X (10.6.8), Final Cut Studio 3

Posted on Nov 3, 2012 12:38 AM

27 replies

zaphod42

Level 1

21 points

Dec 5, 2012 4:22 AM in response to zaphod42

wait .... I tried an advice that I found in this forum to use a different user ... and Motion started up without crashing !?!?!!

so there must be a conflict in my home-directory that Motion 5.0.5 keeps crashing? what could that be?

rcneveu Author

Level 1

4 points

Dec 6, 2012 12:19 PM in response to rcneveu

So Apple has just released udates to FCP X, Compressor, and Motion, that are bug fixes. I'm out of town and can't update till Saturday. If any of you have a chance to try out the new update (Motion 5.0.6), let me know how it works out.

Thanks everybody!

Richard

Dec 6, 2012 9:55 PM in response to rcneveu

I upgraded to 5.0.6 and it crashes every time in the same way for me. I had to Time Machine back to 5.0.4. to get it working again.

rcneveu Author

Level 1

4 points

Dec 9, 2012 1:48 PM in response to Eisen Feuer

Yep, I just tried the update 5.0.6, and it crashed upon launch the same as 5.0.5. Gone back to 5.0.4.

dpcam1

Level 1

4 points

Dec 9, 2012 2:04 PM in response to rcneveu

Hi there...I had lots of problems with FCPX and Motion after the latest updates so I did a clean install of Mountain Lion and then a reinstall of both programs. FCPX certainly behaved better. Motion had a bug to do with using dual monitors, which wasn't improved by the clean install.

Dec 9, 2012 2:08 PM in response to dpcam1

I agree - the bug, unresolved has something to do with mulit monitors, ( so you chooes to use the other setups ' second display, etc) ) but i wonder if itis aslo related to when multiple projects being able ot be open at the same time also is at fault - as thats when it first appeared for us.

Russ H

Level 7

22,432 points

Dec 9, 2012 2:11 PM in response to rcneveu

I noticed from your original post that you have FCS 3 on your system and wondered whether you've followed Apple's installation recommendationsfor having both versions on the same partition…including that part about opening M4 first and then closing.

In my case, I've had the occasional issue with the new apps, but never anything as chronic as your situation – all the while continung to run the FCS 3 apps on the same partition. Typically, a reinstall (of the new apps) and repair permissions has been the solution to any woes.

Russ

dpcam1

Level 1

4 points

Dec 9, 2012 2:26 PM in response to rcneveu

I'm still not convinced they've fixed the dual displays issue. It seems to me that after I put my timing pane on the second monitor, do some work, save, then close Motion, that on opening up the program later Motion hasn't retained the setting for the timing pane on the second monitior. At least the option to extend it out again is still there!!!

zaphod42

Level 1

21 points

Dec 22, 2012 7:31 AM in response to rcneveu

after I discovered that Motion starts up normally by using a different user, I followed Jim Wanamaker's suggestions that I got in another thread to create a copy of my user folder and with this new user to start deleting files and/or folders in the ~/Library until Motion would probably start up.

I promise this is the very last time I would go through all of this and after endless hours&hours&hours&hours spent to find that culprit .... I got him!!!

it was a single smart font collection I created a while ago with Font-Book ... just this one particular deleted and Motion 5.0.6 started up again and seems so far useable again ... hallelujah!!!!

so if anybody has a similar problem, start looking for a culprit here:

~/Library/FontCollections/

start deleting one after the other either through Font-Book or in that folder to get that loved Motion back to do its job (and I hope it will stay that way!)

Feb 8, 2013 5:53 PM in response to zaphod42

Is anyone still having crash prblems or have these all been resolved?

Feb 9, 2013 9:43 AM in response to vinegarman

I am NOT experiecing this spercific problem any more. And as there been no OS or Motion updates I assume cleaning out my 'smart collecitons' ( which i see some of these Apple installs so whats the deal there?) did the trick so i appreciate that tip.

In general our comapny is VERY releiant on Macs. We are experiencing more crashes across the board - from the apps - Motion, Adobe, to the finder, to permission problems, the lack of class they exhibited moving from Final Cut Pro to final cut toy, lack of graphics power, lack of thunderbolt proliferation or support etc., etc.,, that no matter what we do - A. most issues were never here, and now B. seem pretty persistant.

The rumor I heard from inside Apple but with nothing to back this up is that Apple has steered the majority of their developer teams to iOS and they steadily abandon the 'pro apps' and the desktop as a platform in general without the vision and attention to detail they once had.

IOS apps have their place are fun and nice quick bucks but they will never do the whole the job in the real world.

Sorry for the digression.

rcneveu Author

Level 1

4 points

Feb 11, 2013 4:38 PM in response to rcneveu

UPDATE!

Had no time to test any suggested fixes for awhile, but I now have the latest version of Moion running (5.0.6), without any crashes.

What I did was:

1. Trashed the .modulelayout files in: User/"Hidden" Library Folder/Application Support/Motion/Layouts,

and in: User/"Hidden" Library Folder/Application Support/Motion/Layouts/Modified

2. Trashed my Motion Preferences

3. Moved all Font Collections out of: User/"Hidden" Library Folder/Font Collections, to another folder to sequester them.

4. Ran AppStore and updated form Motion 5.0.4 to 5.0.6.

It worked, and has for 5 days now without crashing. And I have since replaced all Font Collections to: User/"Hidded" Library Folder/Font Collections, and Motion 5.0.6 still is running without crashing.

This leads me to believe it was the .modulelayout files. I thought I had tried that previously after reading one of the replies, but perhaps not.

This "Hidden" Library folder can be accessed by option-clicking on the Finder Go Menu, and selecting Library.

I hope this helps some people.

Cheers,

Richard

Message was edited by: rcneveu

Motion 5.0.5 Crashes Upon Launch