# How to create a memory leak in Ignition?

**URL:** <https://forum.inductiveautomation.com/t/how-to-create-a-memory-leak-in-ignition/44039>\
**Category:** Ignition\
**Tags:** ignition80\
**Created:** [March 3, 2021, 1:37pm UTC](https://forum.inductiveautomation.com/t/how-to-create-a-memory-leak-in-ignition/44039 "2021-03-03T13:37:02Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![lrose](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/lrose/32/62724_2.png) [@lrose](https://forum.inductiveautomation.com/u/lrose)\
**Post date:** [March 3, 2021, 2:29pm UTC](https://forum.inductiveautomation.com/t/how-to-create-a-memory-leak-in-ignition/44039/3 "2021-03-03T14:29:09Z")

</div>

> [@Ignition server memory increasing](http://forum.inductiveautomation.com/t/ignition-server-memory-increasing/43932/4):
>
> Firing off async threads without a means to kill off. A single jython async thread stuck in an infinite wait or infinite loop will hold the entire old interpreter in memory after a scripting restart. Opening python sockets without try-finally guards to close. Attaching python listeners to java infrastructure with no way to remove/retire. Caching python objects without control over lifetimes. All of the above are prone to happen regularly as projects are edited and scripts are restarted (pe…

---

_[View the full topic](https://forum.inductiveautomation.com/t/how-to-create-a-memory-leak-in-ignition/44039)._