1 | initial version |
Solved this problem now!!!!
The issue is that my algorithm was relying on an image stabiliser that used some offsets to summarise to detect velocity and indicate whether or not the camera has moved. This stabiliser outputs were a bit sluggish and led to this problem (don't want to explain much details).
I solved it by using a flag that would stop allocating any memory when the camera is in motion. Was tricky to find it though!!