AnsweredAssumed Answered

KillThreadsInPurgatory() eats 16% of CPU

Question asked by PGaganoff on Sep 26, 2011
Latest reply on Sep 30, 2011 by CraigG

Hi!

I have 2 questions:

 

1) After collecting info via Statistical Profiling for 1 hour i got strange arrangement:

killthreads.jpg

As you see, subject function got more than 16% of cycles.

According to this thread  http://ez.analog.com/message/15851#15851,

function KillThreadsInPurgatory() is internal function of IDLE thread, and it is watching for closed threads to clean up.

My application have 5 threads and all of them are opened in the init and never been closed.

My question is what is this function doing for such time, while IdleThread::Run got only 6% itself?

 

2) How much time VisualDSP can be in debugging mode with statistical profiling?

For now Im investigating very annoying bug which leads VDK to hang about every few days. Watchdog resets the system and process repeats in next few days. Trying to catch this issue Im going to leave VDSP running for this days. So Im wondering if it able to do so.

 

Hope this info is wanted not just by me

Thanks in advance, Paul

Outcomes