rtel wrote on Thursday, April 21, 2016:
Is the task in a loop that goes around the read from the queue again.
If you have a VERY SIMPLY demo that is GUARANTEED TO BUILD with no modifications required (so not absolute file paths or anything) that demonstrates you issue then please zip it up and attach it to a post here.
hristozov wrote on Thursday, April 21, 2016:
I can not reproduce the behavior with a simple example but I found, that when I block on a queue with portMAX_DELAY like xQueueReceive( QueueEvent, &new_event, portMAX_DELAY) or any different then zero block time the problem occurs.
If I use xQueueReceive( QueueEvent, &new_event, 0) i.e. block time is zero everything works OK. Any Idea why this happens???
rtel wrote on Thursday, April 21, 2016:
Any Idea why this happens???
No, none.
If you cannot replicate the issue with a simple demo I would suggest
starting with the simple working demo, then add bits in until it goes
wrong - to see what it was that you last did before it stopped working.
I suspect it has nothing to do with the queue and more to do with
memory corruption somewhere - it might be with the simple demo you are
using a different area of memory.