I have a manufacturing application that runs a production rig. I also have a 24/7 logger application running on the same PC, the logger records temperatures and other data about the supporting plant.
Both apps can run independently, but when running at the same time, a TCP/IP link allows the sharing of data between the 2 apps. They normally always run together, but I want them to be robust to the other not being open.
I have a bug, if the logger is not running for a long time, the manufacturing app freezes. This is because the TCP/IP listen is somehow eating up a resource.
The reason for the freeze is that TCP/IP comms with another connected instrument fails. I know this because if I try to open a connection to that instrument using it's dedicated from end software, I get this error:
![20180125_ErrorWhenOpeningEnsembleAfterFreeze.jpg 20180125_ErrorWhenOpeningEnsembleAfterFreeze.jpg]()
When I close the frozen LabVIEW app, I can then open the front end without a windows error.
One explanation of this windows error appears to be "OS runs out of memory for TCP buffers".
Have I implemented the TCP/IP incorrectly? I figure I should check I've not failed to close a TCP/IP related resource?
![20180125_LabVIEWcode01.jpg 20180125_LabVIEWcode01.jpg]()