[Bug?] X-Control Memory Leak with Large Data Array

[jgcode]

Can I continue NI support (discussions etc...) for this CAR here, our should I go back through my local AE?  

Cheers

-JG

[PaulRB]

Hi JG,

Since what you are seeing is expected behavior, I hesitate to create a new CAR. What I would suggest is to post your idea here to let the developers know.

Thanks,

[Jon_S.]

Hi Jon,

If you have more input on this issue I am glad to continue discussion of it.  As of right now the example you have posted is expected and not a bug so to say.  I do think that we should take action on it however.  I think that we need some better documentation about the execution of XControls.  One topic I would like to see us add to the LabVIEW Help is a section "Caveats and Recommendations for using XControls".  This would be similar to the topics on event structure, custom probes, etc.

Do you have other recommendations?  What would have prevented you from getting into this situation and where did you look when you first came about it?

[Intaris]

Just to chime in I've also had problems with this int he past and have posted HERE and tried to get a suggestion on the Idea Exchange (which could maybe be worded better).

It's a killer for me.  I've stopped using XControls because this is a way too big problem to be ignoring.  XControls must have synchronous data updates in order to avoid many of these problems.  At the moment, their data updates are fully asynchronous which means big trouble if your updates are faster than your XControl.

Shane.

[Intaris]

I really think saying thia is not a bug is a slap in the face to anyone seriously trying to go in this direction with XControls and I'd expect better of NI.