I've got a very strange problem with my gateway heap memory. For the last few days it's been climbing erratically to max memory and causing a gateway restart. I did some troubleshooting by removing everything(projects, tags, opc connections, device connections etc). Memory stable after that.
Adding them in one at a time I found that the cause seems to be an opc connection that is perpetually in the "connecting" state. Never faults out. I tried reducing the request timeout from 60 to 10s, and the session timeout from 120 to 30s. No difference.
Any insights into why this would cause a memory heap problem and potential solutions would be appreciated. Obviously I can leave the connection disabled, but I'd like to understand why it's happening in the first place so I can avoid this issue in the future.
Ooooo! That is almost certainly a bug you should report to IA support (open a ticket). I haven't heard of this particular behavior, and memory leaks are always bad.
Is it a connection to a third party server or Ignition's own server?
Never seen this either...
1 Like
It might also be helpful to get a wireshark capture from the gateway to see if the other OPC server is responding strangely or if Ignition is mishandling something.
My bet is on some kind of scripting or timer misuse; usages of things like system.util.invokeAsynchronous or system.tag.readAsync/writeAsync being called repeatedly and stacking up because the underlying operation is taking longer against the offline server than whatever the period of these actions are.
@Torsten_Giesbrecht1 if you already have a support ticket open as I suspect, work with them to provide a heap dump taken while the memory is climbing. If not, open a ticket and then do that 
1 Like
Haven't opened a ticket yet but I'll get on it. It's connecting to a third party server.