Page 1 of 1

Using TaskScan

Posted: Mon Jul 24, 2017 9:55 am
by SeeCwriter
I have an application that starts running very slow after its been running for a while. I used TaskScan to see if that would tell me where the holdup was, but it doesn't operate exactly as the manual says. According to the manual there is supposed to be a plus sign next to stalled tasked that you can click to get more info. But none of the stalled tasks has a plus sign. Every task except #63 & 39 shows an hour glass. The Enet task, #38, says its waiting on fifo for 40 ticks. Isn't that 2-seconds? That seems like a long time when my utility is constantly talking to it via Enet.

Re: Using TaskScan

Posted: Mon Jul 24, 2017 10:13 am
by pbreed
Waiting 2 sec , unless it gets a packet... 2 sec is the timeout....
(Basically the no ethernet traffic received check the link status intervval)

if the ethernet Rx gets a packet the semaphore will be woken up immediately...

Re: Using TaskScan

Posted: Tue Jul 25, 2017 1:05 am
by dciliske
Let me save you a headache: Either install 2.8.5 or patch the OS_SEM::Post bug. I don't know whether this is your issue here, but you will get bit by that...

-Dan