# xQueueSend from Timer Task

**URL:** <https://forums.freertos.org/t/xqueuesend-from-timer-task/6679>\
**Category:** Kernel\
**Created:** [July 16, 2017, 6:29pm UTC](https://forums.freertos.org/t/xqueuesend-from-timer-task/6679 "2017-07-16T18:29:12Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![system](https://d2v6vdsk2p900z.cloudfront.net/original/1X/7fc8fdb729c645aab5b20282bbe34e57cb407be6.jpeg) [@system](https://forums.freertos.org/u/system)\
**Post date:** [July 16, 2017, 6:29pm UTC](https://forums.freertos.org/t/xqueuesend-from-timer-task/6679/1 "2017-07-16T18:29:12Z")

</div>

**[permal](https://sourceforge.net/u/permal/)** wrote on [Sunday, July 16, 2017](https://sourceforge.net/p/freertos/discussion/382005/thread/3738fa88/#e33f):

Hi,

Are there any limitations re. calling xQueueSend from a callback registered via xTimerCreate?

The reason I’m asking is because I get crashes as soon as I call xQueueSend. Moving the exact same code to a regular task works just fine. I have increased the stack size of the TimerTask to 20k so I doubt that it is actually a stack overflow since the code in the callback is literally just this:

```auto
int i = 0;
auto res = xQueueSend(queue, &i, 0);

```

---

<div class="post-metadata">

**Author:** ![system](https://d2v6vdsk2p900z.cloudfront.net/original/1X/7fc8fdb729c645aab5b20282bbe34e57cb407be6.jpeg) [@system](https://forums.freertos.org/u/system)\
**Post date:** [July 16, 2017, 9:15pm UTC](https://forums.freertos.org/t/xqueuesend-from-timer-task/6679/2 "2017-07-16T21:15:27Z")

</div>

**[permal](https://sourceforge.net/u/permal/)** wrote on [Sunday, July 16, 2017](https://sourceforge.net/p/freertos/discussion/382005/thread/3738fa88/#a979):

Please disregard this question. It turns out I had missunderstood how the timer’s ID could be used and the problem I was seeing was a side effect of erroneous pointers.