# Ignition 8 - Memory leak

**URL:** <https://forum.inductiveautomation.com/t/ignition-8-memory-leak/45851>\
**Category:** Ignition\
**Tags:** ignition80\
**Created:** [April 21, 2021, 8:46am UTC](https://forum.inductiveautomation.com/t/ignition-8-memory-leak/45851 "2021-04-21T08:46:41Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![JordanCClark](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jordancclark/32/83362_2.png) [@JordanCClark](https://forum.inductiveautomation.com/u/JordanCClark)\
**Post date:** [April 21, 2021, 9:39am UTC](https://forum.inductiveautomation.com/t/ignition-8-memory-leak/45851/2 "2021-04-21T09:39:25Z")

</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/ignition-8-memory-leak/45851)._