I have a relatively simple TCP server (attached). When connected from a localhost client, the server runs without expanding memory, however, when connected from a network client the memory usage of the server expands rapidly. Two instances of this server VI are opened dynamically and run from the main VI of the application, each with a separate listening port as the input. This VI has been built using LabVIEW 8.2.1. No memory issues arise if no client is connected. What am I missing?

It's hard to tell without the missing globals and other info. Here are some ideas: Try to create the listener once outside the big loop instead of creating a new listener every two seconds (or after each connection). Close the connection only after the big while loop has completed.Whenever the error condition of the big case happens, you have generated a connection ID that never gets closed. Can you probe how often an error occurs here and if so, what error you get?It is possible that when you close the connection and then immediately try to create a new listener on the same port, the port might still be in use finishing up the old connection. Can you attach a fully functional set of VIs (client and server) that demonstrates the problem?

LabVIEW

TCP Memory Leak?

Solved!

This thread was fantastic. Thanks to Ben for pointing it out..

I needed this laugh.. 😄

Message 21 of 21

(1,400 Views)

LabVIEW

TCP Memory Leak?

Re: TCP Memory Leak?