# Memory leak on task deletion with configUSE\_NEWLIB\_REENTRANT

**URL:** <https://forums.freertos.org/t/memory-leak-on-task-deletion-with-configuse-newlib-reentrant/7497>\
**Category:** Kernel\
**Created:** [November 3, 2018, 3:20am UTC](https://forums.freertos.org/t/memory-leak-on-task-deletion-with-configuse-newlib-reentrant/7497 "2018-11-03T03:20:33Z")\
**Posts on this page:** 1\
**Showing post:** 20

<div class="post-metadata">

**Author:** ![hs2](https://avatars.discourse-cdn.com/v4/letter/h/a4c791/32.png) [@hs2](https://forums.freertos.org/u/hs2)\
**Post date:** [November 2, 2020, 4:23pm UTC](https://forums.freertos.org/t/memory-leak-on-task-deletion-with-configuse-newlib-reentrant/7497/20 "2020-11-02T16:23:50Z")

</div>

Yes. Or use an alternative printf version without heap usage like this one:

> [@STM32F429Discovery with STM32Cube, USB, fatfs and FreeRTOS](https://forums.freertos.org/t/stm32f429discovery-with-stm32cube-usb-fatfs-and-freertos/671/7):
>
> I personally like to use [`printf-stdarg.c`](https://github.com/htibosch/freertos_plus_projects/blob/master/plus/Framework/Utilities/printf-stdarg.c)  
> That implementation is ISR-safe, and it has a small use of the stack. However, it does not implement floating point notations.

Note that other (very few) newlib functions might also dynamically allocate memory internally or do that by definition like `strdup`.

---

_[View the full topic](https://forums.freertos.org/t/memory-leak-on-task-deletion-with-configuse-newlib-reentrant/7497)._