# xojo memory leaks

**URL:** <https://forum.xojo.com/t/xojo-memory-leaks/33244>\
**Category:** General\
**Created:** [September 4, 2016, 11:19pm UTC](https://forum.xojo.com/t/xojo-memory-leaks/33244 "2016-09-04T23:19:18Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![dave\_duke](https://forum.xojo.com/letter_avatar_proxy/v4/letter/d/c77e96/32.png) [@dave\_duke](https://forum.xojo.com/u/dave_duke)\
**Post date:** [September 4, 2016, 11:19pm UTC](https://forum.xojo.com/t/xojo-memory-leaks/33244/1 "2016-09-04T23:19:18Z")

</div>

Is there a tool or process to find a memory leak in Xojo, even just seeing the memory which has leaked ( a kernal tool) ?

---

<div class="post-metadata">

**Author:** ![DaveS](https://forum.xojo.com/letter_avatar_proxy/v4/letter/d/848f3c/32.png) [@DaveS](https://forum.xojo.com/u/DaveS)\
**Post date:** [September 4, 2016, 11:57pm UTC](https://forum.xojo.com/t/xojo-memory-leaks/33244/2 "2016-09-04T23:57:40Z")

</div>

- fill the kitchen sink with water
- submerge your app in the sink
- carefully look for memory bubbles

---

<div class="post-metadata">

**Author:** ![Marco\_Hof](https://forum.xojo.com/user_avatar/forum.xojo.com/marco_hof/32/642_2.png) [@Marco\_Hof](https://forum.xojo.com/u/Marco_Hof)\
**Post date:** [September 5, 2016, 12:44am UTC](https://forum.xojo.com/t/xojo-memory-leaks/33244/4 "2016-09-05T00:44:54Z")

</div>

Did you try Xcode’s Instruments? It has a ‘leak’ template.  
Never used it for finding leaks though.

---

<div class="post-metadata">

**Author:** ![DaveS](https://forum.xojo.com/letter_avatar_proxy/v4/letter/d/848f3c/32.png) [@DaveS](https://forum.xojo.com/u/DaveS)\
**Post date:** [September 5, 2016, 1:11am UTC](https://forum.xojo.com/t/xojo-memory-leaks/33244/5 "2016-09-05T01:11:16Z")

</div>

Doubt “Instruments” can help, seeing as it has to link itself to the compiled code, which it can’t do with a XOJO project as XCODE is not the compiler for it.

---

<div class="post-metadata">

**Author:** ![Marco\_Hof](https://forum.xojo.com/user_avatar/forum.xojo.com/marco_hof/32/642_2.png) [@Marco\_Hof](https://forum.xojo.com/u/Marco_Hof)\
**Post date:** [September 5, 2016, 1:18am UTC](https://forum.xojo.com/t/xojo-memory-leaks/33244/6 "2016-09-05T01:18:12Z")

</div>

Did you try it?  
Just open it. Select the Leaks template. Run your App. Select your running App as the target. Hit record. Wait for the red bars.

It won’t point you to the method and line number it’s leaking but you can pretty much guess where it’s coming from.

---

<div class="post-metadata">

**Author:** ![Christian\_Schmitz](https://forum.xojo.com/user_avatar/forum.xojo.com/christian_schmitz/32/158_2.png) [@Christian\_Schmitz](https://forum.xojo.com/u/Christian_Schmitz)\
**Post date:** [September 5, 2016, 7:00am UTC](https://forum.xojo.com/t/xojo-memory-leaks/33244/7 "2016-09-05T07:00:38Z")

</div>

Instruments works well with Xojo.  
I use it often to find leaks in Xojo code or my plugins.  
It can even show you where an object was created in code (call stack)

---

<div class="post-metadata">

**Author:** ![system](https://forum.xojo.com/uploads/default/original/1X/455b4dcc0e61630e9f81940004ddffa49c432a46.png) [@system](https://forum.xojo.com/u/system)\
**Post date:** [October 29, 2020, 6:26pm UTC](https://forum.xojo.com/t/xojo-memory-leaks/33244/8 "2020-10-29T18:26:51Z")

</div>