I tried it before and it not helps. I think, when component tick not actually bind to framerate here takes place some unsynchronization and component tick starts to live with it’s own life.
Here is timeline screenshot. As you can see it is very simple float track.
Thank you for the report, this is definitely a bug. I was able to reproduce this using the steps you provided. However, I also tested this in our latest internal build and it is working as expected now. You should see this working properly in a future release.