Premiere 26.5 Beta 30 Regression causes spurious crashes when third-party plugins invoke PF_UtilitySuite4 GetClipDuration

A regression, first noticed with Premiere 26.5 Beta 30 (but exact build where this appeared is unknown) causes spurious crashes if third-party plug-ins invoke the PF_UtilitySuite4->GetClipDuration() function while handling PF_Cmd_PARAMS_SETUP.

Unfortunately this regression is not 100% reproducible. All our plugins call GetClipDuration() during PF_Cmd_PARAMS_SETUP, and yet the crash occurs only when re-opening certain projects but not others.

The crash is caused by a Null pointer exception internal to Premiere. GetClipDuration() takes only one input parameter, the current in_data->effect_ref, and that pointer is valid. Moreover, just before the call to GetClipDuration(), our plugins are invoking GetClipStart() from the same suite. And that call is working great without crashing.

This is the first version/build of Premiere where this problem as surfaced. The known workaround is to avoid calling GetClipDuration() during PF_Cmd_PARAMS_SETUP, but the unwanted side-effect of this is that any code that relies on knowing that information (how many frames are in the effect clip?) is simply failing to work correctly.