nanguantong

``` int probeSize = 1024*1024; ByteBuffer readBuf = ByteBuffer.allocateDirect(probeSize); AVIOContext iavioCtx = avio_alloc_context(readBuf, probeSize, 0, ifmtCtx, readBufferCbPtr, null, null); ``` Why?

> > > ``` > int probeSize = 1024*1024; > ByteBuffer readBuf = ByteBuffer.allocateDirect(probeSize); > AVIOContext iavioCtx = avio_alloc_context(readBuf, probeSize, 0, ifmtCtx, readBufferCbPtr, null, null); > ``` > > Why?...

> > Make sure to call close() on all objects before returning. We can do that easily with PointerScope. > > Yes, I did. However, the memory still increased slowly...

> > Crash while calling `buf.put(recvBuf, 0, size).`, because out of array index. > > What is recvBuf? byte[] recvBuf = new byte[4096];

So is this a bug for using `Read_packet_Pointer_byte___int` or `Read_packet_Pointer_ByteBuffer_int`?

> > > > > > > > > However, the memory still increased slowly in the step 8K, why? > > You'll need to find where this is happening...

> So is this a bug for using `Read_packet_Pointer_byte___int` or `Read_packet_Pointer_ByteBuffer_int`? And, if I delete `buf.put(recvBuf, 0, size);`, instead of `return 0`; directly, the memory is normal. So the `av_read_frame()`...

So how to use the `Read_packet_Pointer_byte___int` or `Read_packet_Pointer_ByteBuffer_int`?

> > So is this a bug for using `Read_packet_Pointer_byte___int` or `Read_packet_Pointer_ByteBuffer_int`? > > It's not a bug, the size information isn't available from a pointer. You need to take...

``` in app/src/components/Controls/TopBar.js localRecordingState : PropTypes.string fix to localRecordingState : PropTypes.object ```