libgui: make MAX_FRAME_HISTORY a configurable property
Some devices have particularly large pipelines for decoding video. This can result in large queues of decoded frames waiting to be displayed. If the frame event history isn't large enough, then frame events can fall out of the queue before the buffers are actually rendered, which causes failures when processing consumer frame events. Test: manually check that MAX_FRAME_HISTORY is configurable at build Change-Id: I8bfcc6bf095e775c93a39669840d721417a58113
Loading
Please register or sign in to comment