Sergey Sharybin
a4b92a6814
According to the report it is a regression since 3.2, but it is tricky to pin-point which exact commit caused it. The root of the issue is that under certain circumstances frame might be read and processed twice, depending on the order in which panels and the main area is drawn: the footage information panel skips cache, so it it is drawn prior to the main area it leads to 2 frame reads. Opening the Metadata panel triggers code path which forces frame to be put to the cache, solving the double frame read. Solution is simple: do not skip cache when acquiring image buffer for the footage information: the same frame will be needed for the main area as well. Pull Request #104860