Motion 5.0.5 Crashes Upon Launch

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

Reply

Answer 1

BenB

Level 6

12,097 points

Nov 3, 2012 10:41 AM in response to rcneveu

What GPU are you running?

Reply

Answer 2

rcneveu Author

Level 1

4 points

Nov 3, 2012 10:53 AM in response to BenB

It's the ATI Radeon HD 4870 with 512 MB vram.

Reply

Answer 3

Nov 4, 2012 6:31 PM in response to rcneveu

I have the same issues since going to 5.05 - On a 8 core with ATI Radeion 5770 10 GB ram...Motion windows started acting strange - could not get the viewer window open...accirdently opened two projects at once ( a feature brought back i think from motion 4 which we wanted) since then i can not open any motion projects - the windows do not know where to be. trashed and re installed the app from the app store - no difference - so it is some now hidden window draw routine. Projects DO open - but as soon as i touch any options like VIEW - crash.

I too use Preference Manager - but i have noticed in the last week - it would not restore my previous sessions in FCP or Motoin 5 something may have updated negating Pref Manager that has saved us so many times?

Everything else seems rock solid...still atempting to debug or move to another system so we can carry on.

Thanks...

carry on, stay calm.

Reply

Answer 4

Nov 4, 2012 7:22 PM in response to Arthur Bell

To double check i went back to a Preferences Manager from JULY - and that DID restore my Motion ( 5.05) to its proper windows with only one crash.

This is completley anecdotal, but I wonder if the 'open mutiplle projects in Motion that Apple brought back is not quite ready for prime time. We are in the middle of 6 commercial spots so i am not about to test fate anytime soon - but we are upa dn i am glad.

Letys make some more TV.

Reply

Answer 5

Lasse G.

Level 1

0 points

Nov 9, 2012 5:02 AM in response to rcneveu

I have the same problem here.

Reply

Answer 6

rcneveu Author

Level 1

4 points

Nov 14, 2012 5:16 PM in response to rcneveu

Thanks everyone for the replies. I have yet to find a solution to make 5.0.5 work on my machine. I have since reverted back to 5.0.4 through a Time Machine restore, and everthing seems to work as it should. Hopefully Apple will hear our cries, and fix this right away. There does seem to be a few of us.

Thanks again,

Richard

Reply

Answer 7

dpcam1

Level 1

4 points

Nov 16, 2012 6:06 PM in response to rcneveu

Theres definitely buggy when you try to put anything on a second monitor....deleting the layouts folder solves my problem for a while and then it comes back again.

Reply

Answer 8

Russ H

Level 7

22,432 points

Nov 17, 2012 6:54 AM in response to rcneveu

rcneveu wrote:

Hopefully Apple will hear our cries, and fix this right away. There does seem to be a few of us.

Thanks again,

Richard

Richard,

If you want to get Apple's attention, use this Motion feedback link

Russ

Reply

Answer 9

zaphod42

Level 1

21 points

Nov 18, 2012 7:25 AM in response to rcneveu

@rcneveu

how did you managed? which files/folders did you replace with your backup?

I replaced all these without any luck ... what did i miss?

(with a BIG thanks in advance!)

/Applications/Motion.app

~/Movies/Motion Templates

Compositions

Effects

Generators

Titles

Transitions

~/Library/Application Support/Motion

Command Sets

Layouts

Library

Presets

~/Library/Preferences/com.apple.motionapp.plist

/Library/Application Support/ProApps

Reply

Answer 10

rcneveu Author

Level 1

4 points

Nov 19, 2012 10:03 AM in response to zaphod42

@zaphod42,

/Applications/Motion.app is the only thing I restored through Time Machine backup. I did delete all Preferences for Motion in:

Hard Drive/Users/rcneveu/Library/Preferences

I deleted these prefernces using an app called Preference Manager.

Hope this helps.

R

Reply

Answer 11

Nov 19, 2012 10:13 AM in response to rcneveu

Smae with me...Preferences Manager has saved my bacon many times - especialy when Final Cut Pro decided to forget my favorite effects...

http://www.digitalrebellion.com/prefman/

Its free and great, and now it also support Premiere CS 6.

I am sorry if it can not help you going backwards but i bet it will help you going forward.

.../Art

Reply

Answer 12

Nov 26, 2012 10:50 PM in response to rcneveu

I am also in the same boat. New 12 core system and I can't use Motion. I guess my laptop will be getting some abuse this week.

Reply

Answer 13

Claranna

Level 1

0 points

Nov 29, 2012 2:01 AM in response to Arthur Bell

Thank you for your help Arthur : Preference Manager has fixed my problem and Motion 5.0.5 is now working fine without crashing uppon launch...

Finaly, you MUST use Preference Manager with these new Apple products in order to work as well....

It's a brand new PC world ????

Reply

Answer 14

Dec 2, 2012 6:33 PM in response to rcneveu

I Time Machine'd back to 5.0.4 as well, works for me.

Reply

Answer 15

zaphod42

Level 1

21 points

Dec 5, 2012 3:55 AM in response to rcneveu

NOTHING works for me ... not even downgrading to 5.0.2.

after spending endless hours to figure out what the **** is going on ... out of work!

and no one to contact at Apple to get some serious support!

what is left to do? get the competitor's product to finally work again? after all these years working with Motion? learning a new software or hoping for some kind of miracle that Motion starts up again?

Reply