06-19-2009 09:15 AM - edited 06-19-2009 09:16 AM
Pericles,
In my testing, the problem wasn't necessarily due to the queue connection. In the VI that you originally posted I made a third copy of your cluster and wired that to the connector pane instead of the queue (thus having 3 of the Metris_Components clusters connected to the connector pane) and I saw the same LabVIEW: Full of Memory error. I encourage you to try this out on your end and see if you experience the same behavior.
As for your question regarding how you would use the number I provided, with every release of TestStand we provide a Bug Fix List in the ReadMe and a Known Issues List on ni.com. When the next maintenance release or major release of TestStand is shipped, you can use the previously mentioned number to search the Bug Fix List to see if the behavior has been corrected or the Known Issues List to see if it still exists.
Hope this helps!