I’m a new custodian of our gateway and since taking over and having the previous maintainer and developer leave I’ve been having a consistent problem with the memory ramping up to our max allocated over time. I’ve been working to learn where I could look to find things that might be causing this to happen and here is one thing I’ve found that could be a culprit. Could anyone help me out here?
Possibly. But the thread giving the error is dead, so it by itself is not the leak. What it might be setting up and then not clearing when it dies might be a concern. You’ll need to show us the rest of the error, or the corresponding clip from the wrapper log. (Please not a screen-shot–paste text then use the pre-format button.)
SystemUtilities 10Sep2021 15:28:36
Error running function from system.util.invokeAsynchronous
com.inductiveautomation.ignition.common.script.JythonExecException: TypeError: 'NoneType' object is not callable
at org.python.core.Py.TypeError(Py.java:265)
at org.python.core.PyObject.__call__(PyObject.java:409)
at com.inductiveautomation.ignition.common.script.ScriptManager.runFunction(ScriptManager.java:821)
at com.inductiveautomation.ignition.gateway.script.GatewaySystemUtilities.lambda$_invokeAsyncImpl$0(GatewaySystemUtilities.java:139)
at java.base/java.lang.Thread.run(Unknown Source)
Caused by: org.python.core.PyException: TypeError: 'NoneType' object is not callable
... 5 common frames omitted
Thank you for the quick response, I am very new and inexperienced with this specifically and databases in general. It’s a ‘trial by fire’ kind of situation. I used the pre-format button, though I don’t know if I did it correctly.
You’re probably going to have to take runtime histograms or otherwise use java tools to inspect what is going on. You should get support involved directly. (This forum is not support–just interested volunteers.)