# Ignition Service Stop **URL:** \ **Category:** General Discussion\ **Created:** [November 15, 2024, 3:14am UTC](https://forum.inductiveautomation.com/t/ignition-service-stop/98648 "2024-11-15T03:14:52Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![hisyam\_agung](https://avatars.discourse-cdn.com/v4/letter/h/9dc877/32.png) [@hisyam\_agung](https://forum.inductiveautomation.com/u/hisyam_agung)\ **Post date:** [November 15, 2024, 3:14am UTC](https://forum.inductiveautomation.com/t/ignition-service-stop/98648/1 "2024-11-15T03:14:52Z")
Hello guys, I currently have a problem with the use of Ignition. Where the use of memory is suddenly high until it causes Services to stop. I have tried submitting tickets and troubleshooting in meetings to find a solution to this problem. Together with Inductive, we are troubleshooting from checking the Wrapper Log and VMWare Configuration. From these results, no significant problems were found, then directed to check the processes in Ignition such as the use of Tags, Scripts, Expressions and others. Performance conditions when Ignition occurs problems, as follows: ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/9/c/9c27bef373ba0da3e382a66434952d15ae73c09d.png) When an Issue occurs, Waiting Threads can reach more than 100,000 with the following Running Script conditions: ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/3/6/36cb8f03b2c0328f7bff2553236f9c7dbe321d8a.png) After that I tried to find a temporary solution by increasing RAM and Maximum Memory Usage in Configuration. Before: RAM : 32Gb, Max Memory: 20Gb After : RAM : 48Gb, Max Memory : 32Gb. The addition did not produce any results. ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/0/9/09cc708b8a59aa178afd0f2a268b4a9a71aeb2d0.jpeg) I also attached Wrapper Log, Ignition.Conf.. From the above conditions, can you help me to take action that can be done. Because this issue has been going on for 1 month and the information why Running Script runs can be too high to consume large RAM. [wrapper.zip](https://forum.inductiveautomation.com/uploads/short-url/eHXmnrr2n7ekH5YKoso7xeNQqB8.zip) (187.0 KB) ---
**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 15, 2024, 12:21pm UTC](https://forum.inductiveautomation.com/t/ignition-service-stop/98648/2 "2024-11-15T12:21:21Z")
Plain threads like that do not get created by Ignition itself. Something in your own code in Ignition is doing that. Or perhaps in a third-party module. The wrapper log is not what needs to be inspected. It is your entire codebase in your Ignition project(s). You probably won't get that for free, on this forum or elsewhere. ---
**Author:** ![hisyam\_agung](https://avatars.discourse-cdn.com/v4/letter/h/9dc877/32.png) [@hisyam\_agung](https://forum.inductiveautomation.com/u/hisyam_agung)\ **Post date:** [November 16, 2024, 8:43am UTC](https://forum.inductiveautomation.com/t/ignition-service-stop/98648/3 "2024-11-16T08:43:37Z")
Thank you for your advance, After I break down all of the projects, I notice several projects using time.sleep function in their script. And I realized in the forum you answered that if that function can impact it, it will freeze the user interface. > [@Time.sleep function in Ignition](https://forum.inductiveautomation.com/t/time-sleep-function-in-ignition/10337): > > Hi All, Anyone here have tried to to use time.sleep function of time module in Ignition? I tried to use this function but the result is not what I wanted. Below is my sample script: [code]import time for i in range(1, 6): print i time.sleep(3)[/code] In Ignition this will print: 1,2,3,4,5 at the same time. What I wanted is that there will be delay of 3 second for every print. This script works outside Ignition, I wonder why Ignition is not doing the same thing. Anyone can help me with th… ---
**Author:** ![Matrix\_Engineering](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/matrix_engineering/32/19781_2.png) [@Matrix\_Engineering](https://forum.inductiveautomation.com/u/Matrix_Engineering)\ **Post date:** [November 16, 2024, 10:51am UTC](https://forum.inductiveautomation.com/t/ignition-service-stop/98648/4 "2024-11-16T10:51:42Z")
Your memory is increasing over time. It should look like a sawtooth pattern. Increasing RAM is just increasing the time before a crash. If your VM has 48 GB, I recommend setting ignition.conf to 16 GB for both initial and max. Your memory is circa 8GB before the leak starts. There is a server sizing guide that can help with this. ---
**Author:** ![hw79](https://avatars.discourse-cdn.com/v4/letter/h/838e76/32.png) [@hw79](https://forum.inductiveautomation.com/u/hw79)\ **Post date:** [November 22, 2024, 8:04pm UTC](https://forum.inductiveautomation.com/t/ignition-service-stop/98648/5 "2024-11-22T20:04:50Z")
what do your thread pools look like? We had proxy hopping turned on for 30+ gateways and when the EAM had a connection hiccup it caused the threads to spike and would lock up the JVM.