02-15-2012 06:59 PM
Hi Ben,
The CAR number is #336193.
02-23-2012 12:37 AM
Hi Brian,
With more investigation, we have already addressed this issue. The problem is that there's some memory leak in TDMS when handling the string arrays after transposing. The workaround for you probably are:
VIs with the workarounds are attached.
Please feel free to let me know if there's more quesitons.
02-23-2012 07:25 AM
Since this bug still reproduces in LV2011, does that mean it will be fixed in LV2012?
02-23-2012 07:27 AM
Yes, it will be.
02-23-2012 11:18 AM
@YongqingYe wrote:
VIs with the workarounds are attached.
Please feel free to let me know if there's more quesitons.
Hi Yongqing,
Thank you for posting the workarounds which I hope will save others the time and energy that this issue has drained from me. Since my project required an immediate solution, as I mentioned I used the gTDMS VI's as my workaround. However, now I have found another issue which is either in the "TDMS Get Properties" primative or the way that the gTDMS is writting to the TDMS file. Look at the attached VI which demonstrates the problem. The "TDMS Get Properties" primative returns an error when reading a file created by the gTMDS functions and not when using the primatives. Perhaps the reason is that the primatives are writting "NI" properties that are present but getting stripped by the Get Props, which the gTMDS doesn't and there are no properties which is causing the error? Either way, I guess that I would expect the "TDMS Get Properties" to behave the same since in both cases there are no user properties.
Thanks,
Brian
So I guess now my workaround is to go back to the primatives and apply the "AlwaysCopy" workaround. Why do I feel like I'm going in circles...
02-23-2012 12:12 PM
@brian175 wrote:
So I guess now my workaround is to go back to the primatives and apply the "AlwaysCopy" workaround. Why do I feel like I'm going in circles...
Another solution is to write a dummy property to the group which prevents the error.
02-23-2012 11:13 PM
Hi Brian,
I would recommend you use TDMS primitive VIs instead of gTDMS. gTDMS was developed in the time when TDMS was not supported on cRIO VxWorks platform before.
Thank you.
04-11-2012 12:03 PM
Has there been any action here? I may have a similar issue, writing tdms files over time I see a memory leak also. I am tracking down in my code now to see if I have the exact situation described in this thread, but would love to know what is going on.
Thanks,
Rob
04-11-2012 12:05 PM
Nevermind, I just saw the new messages.
Thanks,
Rob
07-10-2013 10:41 AM
Had a similar issue with the Transpose and write to TDMS. Adding 'Always Copy' seems to have fixed it, I'll let you know for sure in 1000 hours since that is how long this application is supposed to run.
Thanks for the workaround!