[Bf-vfx] Confirmation of bug in tomato

[Coen Spoor]

Hi,

Last night I ran into what I think is a bug in the tracking algorithm. 
I did some tracking across 250 frames, and later moved my start frame up 250 frames, to track across those. While in the 250-500 range, there were some frames that had been tracked, according to the ui, but everytime I tried to move a tracker/track blender crashed on me.

I reverted to deleting the path up to that frame, and that worked slightly beter, though not as good as tracking from frame 1-500(and therefor uncached).

Can anyone reproduce this?

Cheers,
Coen Spoor
NachtWerk vfx