3d0c/gmf

readCallback and size of bytes to read

Opened this issue · 1 comments

In readCallback, handlers.readPacket is called without being given the input buffer size from libav. Doesn't it mean readPacket function can overflow the expected size of buffer? I would add two arguments buf and buf_size to readPacket callback. Or am I missing something?

wader commented

I think so, at least buf_size should be passed so that readPacket known maximum buffer size to return