# Memory leaks in LimesuiteNG under MacOS

**URL:** <https://discourse.myriadrf.org/t/memory-leaks-in-limesuiteng-under-macos/12975>\
**Category:** Lime Suite\
**Created:** [7 December 2025 22:36 UTC](https://discourse.myriadrf.org/t/memory-leaks-in-limesuiteng-under-macos/12975 "2025-12-07T22:36:16Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![tkp](https://yyz2.discourse-cdn.com/flex034/user_avatar/discourse.myriadrf.org/tkp/32/4399_2.png) [@tkp](https://discourse.myriadrf.org/u/tkp)\
**Post date:** [7 December 2025 22:36 UTC](https://discourse.myriadrf.org/t/memory-leaks-in-limesuiteng-under-macos/12975/1 "2025-12-07T22:36:17Z")

</div>

Hi-

I didn’t see anything about this posted here, but recently I have been hunting down memory leaks in my code using Profiling in Xcode and see that a number of memory leaks show up that are associated with setting up the GFIR filters in the configuration routine. They aren’t huge memory leaks, but there are quite a few of them. I tried both the stable and develop branches and they show up in each. I am building the libraries using cmake, while my code is built using Xcode. These are not really causing a problem for me since they only show up when the devices are configured, which only happens once per run and I can discard that - I am just mentioning it in case it is of interest.

 ![Screenshot 2025-12-07 at 2.21.59 PM](https://canada1.discourse-cdn.com/flex034/uploads/myriadrf/original/2X/1/1948f4d0355ea366772f2c1b3cc087859f6c6210.jpeg)

---

<div class="post-metadata">

**Author:** ![ricardas](https://yyz2.discourse-cdn.com/flex034/user_avatar/discourse.myriadrf.org/ricardas/32/86_2.png) [@ricardas](https://discourse.myriadrf.org/u/ricardas)\
**Post date:** [8 December 2025 08:01 UTC](https://discourse.myriadrf.org/t/memory-leaks-in-limesuiteng-under-macos/12975/2 "2025-12-08T08:01:05Z")

</div>

Hi, thank you. Leak is fixed [Fix memory leak in GFIR coefficients generation · myriadrf/LimeSuiteNG@75b603d · GitHub](https://github.com/myriadrf/LimeSuiteNG/commit/75b603dfcd17b318e0d7ba1d6497ce3a19650b3a)

---

<div class="post-metadata">

**Author:** ![tkp](https://yyz2.discourse-cdn.com/flex034/user_avatar/discourse.myriadrf.org/tkp/32/4399_2.png) [@tkp](https://discourse.myriadrf.org/u/tkp)\
**Post date:** [8 December 2025 17:58 UTC](https://discourse.myriadrf.org/t/memory-leaks-in-limesuiteng-under-macos/12975/3 "2025-12-08T17:58:31Z")

</div>

Thank you - I see where that goes and will check it out. Appreciate the quick response.

---

<div class="post-metadata">

**Author:** ![tkp](https://yyz2.discourse-cdn.com/flex034/user_avatar/discourse.myriadrf.org/tkp/32/4399_2.png) [@tkp](https://discourse.myriadrf.org/u/tkp)\
**Post date:** [16 December 2025 23:02 UTC](https://discourse.myriadrf.org/t/memory-leaks-in-limesuiteng-under-macos/12975/4 "2025-12-16T23:02:59Z")

</div>

I saw right away after compiling the fix that the memory leaks were still there (I checked to make sure I am compiling the fixed code). However, because I also had leaks in my code I wanted to get rid of those before reporting the persisting leaks. I have now gotten rid of my leaks but the remaining leaked objects are shown below. I am not sure if these are the same ones or not as shown previously - the number reported is about the same (22), and they come from the same part of the code. I have expanded the object references below.

As I said in my original message, these don’t appear to be causing any problem for me, so I am reporting what I see in case it is of any interest. I know memory leaks can be very difficult to track down.

Thanks again for all of your help.

 ![Screenshot 2025-12-16 at 2.56.41 PM](https://canada1.discourse-cdn.com/flex034/uploads/myriadrf/original/2X/6/61a94bf37c2c919a82e94b406bc6634a3356e8dc.jpeg)