Re: FCPX parameterChanged crash
Re: FCPX parameterChanged crash
- Subject: Re: FCPX parameterChanged crash
- From: Paul Schneider <email@hidden>
- Date: Mon, 9 Jan 2012 10:28:23 -0800
Can you send a stack trace of all the threads? Try "thread apply all backtrace" in gdb.
On Jan 9, 2012, at 9:40 AM, Paul Miller wrote:
> On 1/7/2012 2:18 PM, Paul Miller wrote:
>> On 1/7/2012 2:02 PM, Paul Miller wrote:
>>> On 1/7/2012 1:55 PM, Paul Schneider wrote:
>>>>
>>>> Hi Paul,
>>>>
>>>> There's a bug in FCPX which will cause this crash when an FxPlug
>>>> changes parameter 63, and only parameter 63. It should be fixed in an
>>>> upcoming update. If you need to work around it, avoiding ID 63 should
>>>> do the trick. This is radar 10504317 if you need to check on the
>>>> status in the future.
>>>
>>> Paul - er, okay at first I totally thought you were screwing with me!
>>>
>>> That's a great bug!! Will try the workaround and let you know how it
>>> goes!! Thanks for letting me know.
>>
>> Holy cow it works! (I just added 100 to all of my parameter ids).
>>
>> Can you shed any light on how this bug came to be? I bet there is a
>> fascinating back-story to it! :-)
>
> So now we're getting some random hanging while setting the parameters. It's happening more on the other machine I can't debug on (no dev tools). Relevant stack trace:
>
> 10 -[OZFxPlugParameterHandler setFloatValue:toParm:atTime:] + 198 (in Ozone) [0x107a85166]
> 10 -[OZFxPlugParameterHandler preChannelChange:] + 212 (in Ozone) [0x107a81334]
> 10 -[FFChannelChangeContext willSetChannel:flagsOnly:] + 359 (in Flexo) [0x1009c0ff7]
> 10 -[FFChannelAction lockChannels] + 103 (in Flexo) [0x1009c1477]
> 10 -[FFAnchoredSequence _actionBeginEditing] + 45 (in Flexo) [0x100a3e7cd]
> 10 -[FFSharedLock _writeLock] + 120 (in Flexo) [0x100828008]
> 10 -[NSCondition wait] + 261 (in Foundation) [0x7fff94ef9594]
> 10 __psynch_cvwait + 10 (in libsystem_kernel.dylib)
>
>
> Looks like some kind of deadlock. I've tried it both with and without a start/endAction block around the parameter setting code.
>
> Any ideas? Any chance this is related to the mysterious parameter id 63 issue?
>
> Paul - can I get you a test build?
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Pro-apps-dev mailing list (email@hidden)
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Pro-apps-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden