VIDENC1_delete () crashes while freeing mpeg4enc instance

Eric Chartier

I'm trying to track down an enigmatic problem. After some codec "restart" (create/delete cycles) the VIDENC1_delete causes segfault at best and kernel oops at other times.

Here is a backtrace obtained with gdb

Program received signal SIGSEGV, Segmentation fault.

[Switching to LWP 1201]

0x00098d10 in freeResource ()

(gdb) bt

#0 0x00098d10 in freeResource ()

#1 0x00099000 in EDMA3_freeLogicalChannel ()

#2 0x00097968 in IRESMAN_EDMA3CHAN_freeHandle ()

#3 0x0009a348 in RMAN_freeResources ()

#4 0x0004a514 in Algorithm_delete ()

#5 0x000497a8 in VISA_delete ()

#6 0x000453a4 in VIDENC1_delete ()

#7 0x0002840c in CMp4Encoder::Close (this=0x133fb8) at Mp4Encoder.cpp:334

#8 0x0003ecdc in CVideoStreamSrcImpl::StopEncoder (this=0x133dd0)

at VideoStreamSrcCore.cpp:35

I am using dm365 with dvsdk_3_10_00_19. My mpeg4enc version is 2_00_00_07.

I am not certain about how to tackle this problem since it happen once in 50 - 100 times, sometimes more.

over 14 years ago

0 Gunjan over 14 years ago

TI__Expert 7415 points

Could you tell me what version of Framework Components is being used by that DVSDK ?

Do you also see this issue if you have trace enabled for FC ? http://processors.wiki.ti.com/index.php/Trace_in_Framework_Components#Framework_Components_2.22_and_later_2.x_releases

0 Eric Chartier over 14 years ago in reply to Gunjan

Prodigy 220 points

I'm using framework 2.25.2.6

I can modify my config file according to the link you've provided under "Set up GT" and "Enable trace/debug for individual or all FC modules". I'm only using

xdc.useModule('ti.sdo.fc.global.Settings').profile = "debug_trace";

0 Eric Chartier over 14 years ago in reply to Eric Chartier

Prodigy 220 points

I have trouble recreating the error with CE_DEBUG=2 because of the sheer amount of debug log getting printed to the console. This somehow breaks my streams timing and causes other errors

0 Gunjan over 14 years ago in reply to Eric Chartier

TI__Expert 7415 points

Hmm.. if not CE_DEBUG, could you link in "debug" version of FC libraries, and provide some line numbers using the "bt" trace ? Rebuild with xdc.useModule('ti.sdo.fc.global.Settings').profile = "debug";

If not trace, it would be good to know what lines the error comes out of, we might be able to work back from there.

0 Eric Chartier over 14 years ago in reply to Gunjan

Prodigy 220 points

I'm starting to think that my application could be corrupting heap at some point. I get a lot of seemingly unrelated errors.

I tried cross-compiling valgrind for dm365 but it does not seem to be supported. Only armv7 seem to be ok on the arm architecture.

Is there any other similar tool I could use?

0 Gunjan over 14 years ago in reply to Eric Chartier

TI__Expert 7415 points

No, unfortunately I'm not aware of any tool to do this..

Processors

Processors forum

VIDENC1_delete () crashes while freeing mpeg4enc instance