# High memory usage alert

**URL:** <https://forum.inductiveautomation.com/t/high-memory-usage-alert/112298>\
**Category:** Ignition\
**Tags:** ignition81\
**Created:** [November 20, 2025, 7:33am UTC](https://forum.inductiveautomation.com/t/high-memory-usage-alert/112298 "2025-11-20T07:33:42Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![aryavani.m](https://avatars.discourse-cdn.com/v4/letter/a/9fc29f/32.png) [@aryavani.m](https://forum.inductiveautomation.com/u/aryavani.m)\
**Post date:** [November 20, 2025, 7:33am UTC](https://forum.inductiveautomation.com/t/high-memory-usage-alert/112298/1 "2025-11-20T07:33:42Z")

</div>

Hi All,

we are facing a high memory usage alert in one of our server. We tried increasing the memory but still the memory is hitting to 90%. Need a support in troubleshooting which can possibly consume more memory. we have few time scripts and tag change scripts but most of them are basic python scripting. we have time script that uses system.device . restart function. can this cause memory leak? or what could be the possible reason.

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/7/8/78b1a610c1f489fee06435bb4d08aaeb9ba941ae.png)

---

<div class="post-metadata">

**Author:** ![robertm](https://avatars.discourse-cdn.com/v4/letter/r/ea5d25/32.png) [@robertm](https://forum.inductiveautomation.com/u/robertm)\
**Post date:** [November 20, 2025, 10:22am UTC](https://forum.inductiveautomation.com/t/high-memory-usage-alert/112298/2 "2025-11-20T10:22:13Z")

</div>

There's many possibilities, but without you posting examples of your scripts, impossible to guess. It will require examination of code and scripts to potentially find the culprit.

Some possible contributors: are you using global variables/dictionaries

Could you have an infinite loop

Are you running gateway scripts outside of project libraries

For quickest resolution, open a support ticket and have IA examine your system. Will be difficult to pinpoint a cause here, unless you're prepared to start posting suspect scripts.

---

<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:** [November 20, 2025, 1:53pm UTC](https://forum.inductiveautomation.com/t/high-memory-usage-alert/112298/3 "2025-11-20T13:53:28Z")

</div>

Some similar discussions:

> [@Gateway Performance Issues and Tuning](https://forum.inductiveautomation.com/t/gateway-performance-issues-and-tuning/67109/7):
>
> To look at the files you get, you will want "JDK Mission Control" and/or "VisualVM". I like the latter for looking at HPROF dumps.

> [@Ignition JVM Application Monitoring](https://forum.inductiveautomation.com/t/ignition-jvm-application-monitoring/69727/2):
>
> I've been using VisualVM, making remote JMX connections to my Ignition instances. The ability to easily diff snapshots then drill down into heap dumps has been very helpful.

> [@How to find memory leaks in scripts?](https://forum.inductiveautomation.com/t/how-to-find-memory-leaks-in-scripts/75568/3):
>
> Turn off the suspects for long enough to see if the problem stops growing. If you cannot do that, VisualVM profiling combined with heap dumps. But be aware that such profile can cause breakage on its own--it is very invasive and can cause pathological execution pauses.

> [@Ignition Memory Usage](https://forum.inductiveautomation.com/t/ignition-memory-usage/64186/17):
>
> The heap memory usage in a JVM is not categorized conveniently, so you need some knowledge of Ignition's architecture to dig around, but heap dumps (via jmap or jcmd) or heap monitoring (like in VisualVM) are the techniques to use. There's a great deal of "noise" in a normal sawtooth pattern, so I usually use a multiple heap dumps over time, taken at the bottom of a sawtooth, to try to zero in on what is growing.