Labview webserver quitting problem

[skysurfer]

I am using Labview 10 with crio9074. When I start the webserver, Labview completely quits after about an hour. Any suggestions?

[Jamie_S.]

Hi Skysurfer,

I'm Jamie an Applications Engineer at NI UK.

One reason why the webserver may be hanging/quitting is the overuse of sockets with constantly opening and closing TCP connections, this can use up all available sockets and result in the TCP connection locking up. If this is the case ensure that any Open and Close functions are located outside structures where possible, especially while loops.

Hope this helps with your cRIO application.

Thanks

Jamie

[skysurfer]

Thanks for the reply. I don't use any open or close functions.

[Kyle_K]

You may want to watch your ram to see if you have a memory leak. This is just a shot in the dark, some more information about your setup would be useful.

Kyle K.

[skysurfer]

Thanks for the reply. I'm using LV 10. Attached is a sample program that I wrote that updates a graph for every iteration of the while loop. When I use the web server, Labview totally shuts down after about an hour of running. I've noticed in the Remote Panel Connection Manager that the Total Bytes/sec constantly increases to a value of 1.6M before the program shuts down. I believe this has something to do with the problem. Any suggestions?

[johnsold]

You are building 6 arrays in the loop. Plus you get several extra copies for the graph.  Those arrays will keep growing until you have memory allocation problems. The better way is to decide on the maximum size you need for the arrays and initialize the arrays outside the loop.  Then inside the loop use Replace Array Subset to pu tthe data values into the arrays.  No arrays growing, no change in memory usage.

Also, the graph is about 540 pixels wide.  If you send more than 540 points (per plot) to the graph, LV will reduce it to the number of pixels anyway, so why waste the bandwidth.  Do the data reduction before passing it to the graph.

Lynn 

[johnsold]

I speeded up your VI by a factor of 100 and found that the memory usage goes from about 8 KB at the beginning to over 2 MB after an hour.

Lynn

[skysurfer]

Lynn,

Thanks for your input.