# Ignition server memory increasing

**URL:** <https://forum.inductiveautomation.com/t/ignition-server-memory-increasing/43932>\
**Category:** Ignition\
**Created:** [March 1, 2021, 11:02am UTC](https://forum.inductiveautomation.com/t/ignition-server-memory-increasing/43932 "2021-03-01T11:02:53Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [March 2, 2021, 12:18am UTC](https://forum.inductiveautomation.com/t/ignition-server-memory-increasing/43932/4 "2021-03-02T00:18:18Z")

</div>

> [@maja](#):
>
> How can scripting lead to memory leaks?

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 (per project in the gateway).

---

_[View the full topic](https://forum.inductiveautomation.com/t/ignition-server-memory-increasing/43932)._