Val Doroshchuk
Val Doroshchuk
pbuf seems ok than, but newTextureWithDescriptor interesting does it require to release this texture, or it creates everytime new.
> QList textures = { 0, 0 }; Exactly means that no textures are used and no HW accel for rendering. Means textures are leaking here.
> You mean that the QtMM code handling the display (which called handle()) sees that there are no textures returned, and switches to a different way of rendering? Very probable,...
>>Means textures are leaking here. >Yes, but that's then in QtMM code, right? >Or, as a workaround, can we keep a handle on these textures and release their memory later,...
does it mean that MacOS does not reproduce the issue? regardless how long it works?
could you check if you return empty textures QList textures = { 0, 0 }; but keep calling textures[i] = quint64([m_hw->device newTextureWithDescriptor:desc iosurface:surface plane:i]); ? trying to understand where it...
maybe it needs double CVPixelBufferRelease(m_hw->pbuf); ?
or there is an issue inside QtMM, can you try just QtMM?
>uninitialized QAVPacket / AVPacket is used in the following processing and avcodec_send_packet() ? looks you are right, thanks, hope it is the same as you got on mac too
did you print out result of av_read_frame? why it failed