OMAP4 Blaze tablet 2( Encoder/Decoder)

The memory leaks prints when using 2 or more components doesn't reflect a real memory leak, it is part of initial code that was when running only one component, for multiple components like when running Camera and Video Encoder where state changes are mixed those prints are not reflecting a real memory leak.

Can you say more about the test case? are you using Stagefright? or a custom application base in DOMX? used release is 4AI1.7 or 4AI1.4?

This information is to know if there could be some way that come buffers and native surface buffers are not being freed by the application or similar error. Could you share some log?

Thanks for your response.

Values(in bytes) printed in this memory leak keep differing

starting from small value to some maximum and then again starts from small

value,namely in camera module (omx_iss_cam.c file),encoder module(OMX_H264VideoEncoder.c file),

and decoder module(omx_video_decoder.c). A part from memory leak log in ducati bin, we are getting following "Out

of Memory " print  also resulting in Memory allocation failue in ducati bin:-

[CORE1]: [   3226.496] ti.sysbios.heaps.HeapMem: line 296: out of memory: handle=0x80420224, size=2359332
3226.496] ti.sysbios.heaps.HeapMem: line 296: out of memory: handle=0x80420224, size=2359332
[CORE1]: [   3226.496] Depreciated API: ERROR: bios6/src/timm_osal_memory.c:[324]:Memory Allocation failed!!!

Android Release:- 4AI.1.4

It is Custom application.

Use Case:- After ending video call from Blaze to video end point and then again starting

the call, after 3rd trial ,encoder or decoder stops working.

Sulekha,

Sorry for the delay in the answer.

If it is a Custom application it is not possible to support it, since it could be difficult to know if you are using the same code and sequences that for example VTC application.

Trying to find what is wrong could take long time since it could be a thread issue, a incorrect sequence, incorrect values, not setting correct port index, not using hardware/ti/domx/include as DOMX include directory ( this could lead to incorrect indexes, other directory is inside omap4xxx/domx/include that is used for other purposes)  and other possible issues. And other issue could be that your approach is not DOMX it is IOMX just below Stagefright, VTC uses IOMX.

About the error you are seeing, DCC could be harmless, the framerate check in VTC code how it is done there are some values that needs to be set before in order to accept it, about buffer allocation compare code in next link to see if it is the same, there is a flag that is added to indicate buffer type of native or not.

But we have a VTC application code that is functional that must help you to check if the state transitions are correct, and what values are used for OMX_UseBuffer and how to allocate Native buffers and when to free them, between other stuffs.

Post related to VTC application code

http://e2e.ti.com/support/omap/f/849/p/197672/705258.aspx#705258

http://e2e.ti.com/support/omap/f/849/p/178679/661450.aspx#661450

port reconfiguration issues

http://e2e.ti.com/support/omap/f/849/p/210475/747744.aspx#747744

This is one post with similar issues about AllocateBuffer

http://e2e.ti.com/support/omap/f/849/p/192654/689896.aspx

Thanks for your reply.

Could you please answer my following query,so that I can find root cause of the problem.

1) When do we get following error :D/DOMX    (  126): hardware/ti/domx/domx/omx_proxy_common/src/omx_proxy_common.c:529    PROXY_EmptyThisBuffer()    
D/DOMX    (  126): ERROR: failed check:(eError == OMX_ErrorNone) || (eError == OMX_ErrorNoMore) - returning error: 0x80001005 - Error returned from OMX API in ducati

2)what is exact difference between DOMX and IOMX ? as you said "And other issue could be that your approach is not DOMX it is IOMX just below Stagefright, VTC uses IOMX."What issues can be caused by this ?

3)when do we get following error:

hardware/ti/domx/domx/omx_proxy_common/src/omx_proxy_common.c:703 PROXY_AllocateBuffer()

D/DOMX ( 128): ERROR: PROXY_UseBuffer in PROXY_AllocateBuffer failed with error -2147479528 (0x80001018)

E/OMXNodeInstance( 128): OMX_AllocateBuffer failed with error -2147479528 (0x80001018)

E/PlcmOMXCodec( 635): allocate_buffer_with_backup failed

Thanks in advance.

Sulekha

For 1)

By checking the code it is trying to allocate memory for Buffer Mark procedure, can you confirm that is the case? code block starts with hMarkTargetComponent check then there is a check for marked component to be correct or not, if this is the case and you are not using buffer mark you need to set those buffer header pointers to zero. For allocation line it has a specific Malloc failed message that seems not present from your log.

For 2)

The difference between DOMX and IOMX, DOMX is the standard OpenMax IL specification, where you load the OMX_Core library and access the functions by the spec. IOMX is a interface provided by Android FS to access DOMX, this library is used by Stagefright.

For 3)

From OpenMax specification 1.0, this table is not in later versions of the file, it indicates that you are calling buffer allocation at an incorrect state.

http://www.khronos.org/files/openmax_il_spec_1_0.pdf

page 43,

OMX_ErrorIncorrectStateOperation = 0x80001018