LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Compiler error

Do you have any idea how much memory that cluster is taking up?

 

I see there are a lot of arrays and waveform datatypes in there.  Are they growing in size during operation?  If there is a lot of memory being used, or those arrays and waveforms are growing during operation, then I can see why you would be concerned about buffer allocations.  But if that is the case, then perhaps the supercluster should be broken in a couple of smaller clusters with like data grouped together.

0 Kudos
Message 11 of 13
(717 Views)

In a particularly pathological case, the waveforms array could grow larger than 2500*1000*8 bytes = 20 MB in size.  Several of the others will probably grow to about a hundred kB or so.  I'll probably end up splitting the waveforms array out at some point, but the cluster itself is probably still over a megabyte in size without it.  I'd prefer to avoid allocations of that when possible.

 

Thanks!

0 Kudos
Message 12 of 13
(714 Views)

Hello Everyone,

 

This has been reported to R&D (CAR #180608) for further investigation.  A work around for this issue is to either not bundle elements inside the In Place Elements Structure if tthe elements were from the original unbundle on the In Place Elements structure itself.  Another option would be to not use the In Place Elements structure in this case.

Regards,

Jon S.
National Instruments
LabVIEW NXG Product Owner
0 Kudos
Message 13 of 13
(643 Views)