# Memory leak libcanrad

**URL:** <https://forum.opencyphal.org/t/memory-leak-libcanrad/1611>\
**Category:** Libcanard\
**Created:** [March 12, 2022, 8:04pm UTC](https://forum.opencyphal.org/t/memory-leak-libcanrad/1611 "2022-03-12T20:04:53Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![teremok](https://forum.opencyphal.org/letter_avatar_proxy/v4/letter/t/f4b2a3/32.png) [@teremok](https://forum.opencyphal.org/u/teremok)\
**Post date:** [March 12, 2022, 8:04pm UTC](https://forum.opencyphal.org/t/memory-leak-libcanrad/1611/1 "2022-03-12T20:04:54Z")

</div>

When using the module, we periodically observe that the canardFree is trying to release the null pointer.  
canardAlloc: 30688416 bytes: 40  
canardFree: 30688416  
canardAlloc: 31360032 bytes: 32  
canardAlloc: 30720600 bytes: 12  
canardFree nullptr

Can you tell me how to solve this problem? We use version 1.1

---

<div class="post-metadata">

**Author:** ![pavel.kirienko](https://forum.opencyphal.org/user_avatar/forum.opencyphal.org/pavel.kirienko/32/9_2.png) [@pavel.kirienko](https://forum.opencyphal.org/u/pavel.kirienko)\
**Post date:** [March 13, 2022, 12:18am UTC](https://forum.opencyphal.org/t/memory-leak-libcanrad/1611/2 "2022-03-13T00:18:16Z")

</div>

This is not a problem. Freeing a null pointer is a no-op, and it is well-specified.

> <https://github.com/UAVCAN/libcanard/blob/224adff8eb191426dc3ae39f265ea72aa7d1e559/libcanard/canard.h#L354>
