3 of 3 people found this helpful
The problem tag is a Float64. Are any of the previous 527 tags also Float64? For instance, if they were all Float32 then they would use less memory than a Float64, even though they would have the same number of AFValues (around 47808).
The other thing is: are you saving the results to another collection? I see an object named Data2Return but it is obscured in the image. For each tag being processed, is it's data being added to Data2Return? You might say "But the exception is thrown on the preceding InterpolatedValues call." But that would mean that Data2Return is taking up memory for the first 527 tags that the call for the 528th fails.
Hi Rick, it could be possible the problem is the one related to the data2Return object.
The strange thing is that it happened on a 64GB RAM machine and we were not using all the memory.
Anyway the problem was resolved compiling it in x64 instead of Any CPU, maybe there was bad configuration in the compiling options.
2 of 2 people found this helpful
A caution I would give on using Any CPU is that you will want to un-check the "Prefer 32-bit" build option.