>
> Hi,
>
>
> On 05/18/2018 02:50 PM, Frediano Ziglio wrote:
> >> Hi,
> >>
> >>
> >> On 04/19/2018 03:28 PM, Frediano Ziglio wrote:
> >>> display_queue is queued with decoded frames ready to be displayed.
> >>> However current code can insert a timeout before displaying and
> >>> removing the qu
Hi,
On 05/18/2018 02:50 PM, Frediano Ziglio wrote:
Hi,
On 04/19/2018 03:28 PM, Frediano Ziglio wrote:
display_queue is queued with decoded frames ready to be displayed.
However current code can insert a timeout before displaying and
removing the queued frames. As the frames are not compresse
>
> Hi,
>
>
> On 04/19/2018 03:28 PM, Frediano Ziglio wrote:
> > display_queue is queued with decoded frames ready to be displayed.
> > However current code can insert a timeout before displaying and
> > removing the queued frames. As the frames are not compressed the
> > usage of memory by this
Hi,
On 04/19/2018 03:28 PM, Frediano Ziglio wrote:
display_queue is queued with decoded frames ready to be displayed.
However current code can insert a timeout before displaying and
removing the queued frames. As the frames are not compressed the
usage of memory by this queue can became in some
display_queue is queued with decoded frames ready to be displayed.
However current code can insert a timeout before displaying and
removing the queued frames. As the frames are not compressed the
usage of memory by this queue can became in some cases quite
huge (in the order of different gigabytes)
