Jitter crash


    Jan 16 2006 | 5:42 pm
    Please help!
    I had to re-authorise Jitter 1.5.2 because of a conflict with an earlier demo version and now whenever I read a movie into a jitter help file, Max/MSP crashes. This worked fine before.
    I deleted the preferences and restarted to no avail.
    Here is the latest crash log: ***** Date/Time: 2006-01-16 12:27:43 -0500 OS Version: 10.2.8 (Build 6R73)
    Command: MaxMSP 4.5.app PID: 408
    Exception: EXC_BAD_ACCESS (0x0001) Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000000
    Thread 0 Crashed: #0 0x024da6f4 in 0x24da6f4 #1 0x023a81bc in jit_qt_movie_open #2 0x023a6ea4 in jit_qt_movie_readfile_complete #3 0x023a6c18 in jit_qt_movie_readfile_makespec #4 0x023a69cc in jit_qt_movie_readfile #5 0x024b3310 in jit_qt_movie_method_typed #6 0x024b33dc in jit_qt_movie_proxy_method #7 0x023e5af0 in jit_qt_movie_read_typed #8 0x0030ae60 in object_method_typedfun #9 0x0030ad40 in object_method_typed #10 0x0237bbfc in max_jit_obex_gimmeback_dumpout #11 0x02377530 in max_jit_usurp_qfn #12 0x02376a98 in jit_usurp_method #13 0x0237747c in max_jit_usurp_method #14 0x0020d240 in typedmess_fun #15 0x002df640 in outlet_anything #16 0x0020d240 in typedmess_fun #17 0x0020ca1c in typedmess #18 0x0020dfbc in aeval #19 0x001e1fe0 in atombuf_eval #20 0x002a879c in vmessage_bang__FP9_vmessage #21 0x002a9278 in vmessage_click__FP9_vmessage #22 0x001e75a8 in box_click #23 0x00213e20 in 0x213e20 #24 0x002148cc in patcher_click #25 0x0024ea04 in wind_click #26 0x0024de58 in 0x24de58 #27 0x0020397c in 0x20397c #28 0x969a2c54 in DispatchEventToHandlers #29 0x969a2fbc in SendEventToEventTargetInternal #30 0x969b5494 in SendEventToEventTarget #31 0x969c07ac in _Z25HandleMouseEventForWindowP15OpaqueWindowPtrP14OpaqueEven tReft #32 0x969b9934 in _Z16HandleMouseEventP14OpaqueEventRef #33 0x969b287c in _Z29ToolboxEventDispatcherHandlerP25OpaqueEventHandlerCallRe fP14OpaqueEventRefPv #34 0x969a2d0c in DispatchEventToHandlers #35 0x969a2fbc in SendEventToEventTargetInternal #36 0x969b5494 in SendEventToEventTarget #37 0x969b7258 in _Z22ToolboxEventDispatcherP14OpaqueEventRef #38 0x96ab4e38 in HLTBEventDispatcher #39 0x96ab4d08 in RunApplicationEventLoop #40 0x00203430 in app_run #41 0x0020225c in main
    Thread 1: #0 0x90042588 in semaphore_timedwait_signal_trap #1 0x9003e7b4 in _pthread_cond_wait #2 0x90233198 in TSWaitOnSemaphoreCommon #3 0x9023bf78 in TimerThread #4 0x90020c28 in _pthread_body
    Thread 2: #0 0x9003e9a8 in semaphore_wait_signal_trap #1 0x9003e7c4 in _pthread_cond_wait #2 0x9023317c in TSWaitOnSemaphoreCommon #3 0x90233abc in DeferredTaskThread #4 0x90020c28 in _pthread_body
    Thread 3: #0 0x90073ba8 in mach_msg_trap #1 0x90005ed0 in mach_msg #2 0x953ddd60 in _ZN15XServerMachPort14ReceiveMessageERiPvS0_ #3 0x953d1798 in _ZN16MIDIInPortThread3RunEv #4 0x953d55dc in _ZN7XThread9RunHelperEPv #5 0x90020c28 in _pthread_body
    Thread 4: #0 0x90073ba8 in mach_msg_trap #1 0x90005ed0 in mach_msg #2 0x90148938 in __CFRunLoopRun #3 0x90180f04 in CFRunLoopRunSpecific #4 0x94652f80 in _ZN10HALRunLoop9OwnThreadEPv #5 0x946591e0 in _ZN9CAPThread5EntryEPS_ #6 0x90020c28 in _pthread_body
    Thread 5: #0 0x90073ba8 in mach_msg_trap #1 0x90005ed0 in mach_msg #2 0x9676d9dc in JNI_CreateJavaVM_Impl #3 0x9676db60 in JNI_CreateJavaVM_Impl #4 0x96766c7c in JVM_IsSupportedJNIVersion #5 0x90020c28 in _pthread_body
    Thread 6: #0 0x90073ba8 in mach_msg_trap #1 0x90005ed0 in mach_msg #2 0x96698730 in __cmpdi2 #3 0x966d172c in JVM_FillInStackTrace #4 0x966e2e8c in JVM_RawMonitorEnter #5 0x968630ac in JVM_UnloadLibrary #6 0x96766c7c in JVM_IsSupportedJNIVersion #7 0x90020c28 in _pthread_body
    Thread 7: #0 0x90073ba8 in mach_msg_trap #1 0x90005ed0 in mach_msg #2 0x96698694 in __cmpdi2 #3 0x966da344 in JVM_GetCPFieldSignatureUTF #4 0x966fdfac in JVM_GetMethodIxModifiers #5 0x966fb248 in JVM_MonitorWait #6 0x03c75580 in 0x3c75580 #7 0x03c6efb0 in 0x3c6efb0 #8 0x03c6efb0 in 0x3c6efb0 #9 0x03c6c16c in 0x3c6c16c #10 0x966a8db8 in JVM_Read #11 0x96753234 in JVM_StartThread #12 0x96758340 in JVM_GC #13 0x967582d4 in JVM_GC #14 0x96746774 in JVM_GetClassInterfaces #15 0x96766c7c in JVM_IsSupportedJNIVersion #16 0x90020c28 in _pthread_body
    Thread 8: #0 0x90073ba8 in mach_msg_trap #1 0x90005ed0 in mach_msg #2 0x96698694 in __cmpdi2 #3 0x966da344 in JVM_GetCPFieldSignatureUTF #4 0x966fdfac in JVM_GetMethodIxModifiers #5 0x966fb248 in JVM_MonitorWait #6 0x03c75580 in 0x3c75580 #7 0x03c6efb0 in 0x3c6efb0 #8 0x03c6eec0 in 0x3c6eec0 #9 0x03c6eec0 in 0x3c6eec0 #10 0x03c6c16c in 0x3c6c16c #11 0x966a8db8 in JVM_Read #12 0x96753234 in JVM_StartThread #13 0x96758340 in JVM_GC #14 0x967582d4 in JVM_GC #15 0x96746774 in JVM_GetClassInterfaces #16 0x96766c7c in JVM_IsSupportedJNIVersion #17 0x90020c28 in _pthread_body
    Thread 9: #0 0x90073ba8 in mach_msg_trap #1 0x90005ed0 in mach_msg #2 0x96698730 in __cmpdi2 #3 0x966a3314 in JVM_CurrentTimeMillis #4 0x966a33b0 in JVM_CurrentTimeMillis #5 0x96766c7c in JVM_IsSupportedJNIVersion #6 0x90020c28 in _pthread_body
    Thread 10: #0 0x90034728 in semaphore_wait_trap #1 0x9676767c in JVM_IsSupportedJNIVersion #2 0x96767464 in JVM_IsSupportedJNIVersion #3 0x96746774 in JVM_GetClassInterfaces #4 0x96766c7c in JVM_IsSupportedJNIVersion #5 0x90020c28 in _pthread_body
    Thread 11: #0 0x90073ba8 in mach_msg_trap #1 0x90005ed0 in mach_msg #2 0x96698694 in __cmpdi2 #3 0x966d178c in JVM_FillInStackTrace #4 0x9670d08c in JVM_IsConstructorIx #5 0x966edee0 in JVM_RawMonitorEnter #6 0x96746774 in JVM_GetClassInterfaces #7 0x96766c7c in JVM_IsSupportedJNIVersion #8 0x90020c28 in _pthread_body
    Thread 12: #0 0x9003e9a8 in semaphore_wait_signal_trap #1 0x9003e7c4 in _pthread_cond_wait #2 0x002e1ad8 in systhread_cond_wait #3 0x024b3a24 in jit_qt_movie_worker #4 0x002e106c in systhread_threadproc__FPv #5 0x90020c28 in _pthread_body
    Thread 13: #0 0x90042588 in semaphore_timedwait_signal_trap #1 0x9003e7b4 in _pthread_cond_wait #2 0x9022ffa4 in MPWaitOnQueue #3 0x90736fc4 in _ZN13TNodeSyncTask12SyncTaskProcEPv #4 0x9025e364 in PrivateMPEntryPoint #5 0x90020c28 in _pthread_body
    PPC Thread State: srr0: 0x024da6f4 srr1: 0x0200f030 vrsave: 0x00000000 xer: 0x20000000 lr: 0x023a8ad4 ctr: 0x90000e20 mq: 0x00000000 r0: 0x00000001 r1: 0xbfffbc40 r2: 0x02516000 r3: 0x072e4394 r4: 0x00000000 r5: 0x76696465 r6: 0x00000000 r7: 0xa4741688 r8: 0x00000000 r9: 0x001d639c r10: 0x44022240 r11: 0x947418c0 r12: 0x00000000 r13: 0x00000000 r14: 0x00000000 r15: 0x00000000 r16: 0x00000000 r17: 0x072c9219 r18: 0x0061ef30 r19: 0x00000000 r20: 0x00630625 r21: 0x006305e0 r22: 0x00640ea0 r23: 0x00000000 r24: 0x0253714c r25: 0x025370a8 r26: 0x00000000 r27: 0x025f14d0 r28: 0x00000002 r29: 0x00000000 r30: 0x0251a044 r31: 0x025f14d0

    • Jan 16 2006 | 6:32 pm
      Andrea, you can't use Jitter under 10.2.x, as mentioned in the requirements section of the website. Updating to 10.3.x will solve this problem.
      jb
      Am 16.01.2006 um 18:42 schrieb Andrea:
      > > Please help! > > I had to re-authorise Jitter 1.5.2 because of a conflict with an > earlier demo version and now whenever I read a movie into a jitter > help file, Max/MSP crashes. This worked fine before. > > I deleted the preferences and restarted to no avail. > > Here is the latest crash log: > ***** > Date/Time: 2006-01-16 12:27:43 -0500 > OS Version: 10.2.8 (Build 6R73)
    • Jan 16 2006 | 6:41 pm
      Thanks, but as I said I was able to run it with no problem under 10.2.8 before??? Same machine, same OS, same software. Please help, my laptop can't run 10.3.
    • Jan 16 2006 | 6:51 pm
      Or, since I purchased 1.5.5 is it possible to run version Jitter 1.2.4 until I get a new laptop that will run OSX10.3 or higher?