Sign Up
EU Cyber Resilience Act (CRA) — First Deadline September 2026
If you sell LabVIEW-based software and systems in the EU, please be aware that new CRA regulations may require you to implement security vulnerability reporting starting September 11, 2026. The VIPM Team has prepared guides to help you understand how this applies to your software applications and published packages, since it's important you understand these regulatory requirements (click the Learn More link to read these guides). Thank you for your help in keeping security front-and-center within the LabVIEW community.
Learn more
VIPM › Posts › Re-entrancy Issue for Multiple-instances of Logger

suggestion

Re-entrancy Issue for Multiple-instances of Logger

Suggestion shared 2 years, 8 months ago by Steven Dusing
   

Details

I'm using the Size TDMS.lvclass

The "Elapsed Timer Non Express Core.vi" is a preallocated clone called by the shared clone reentrant vi "Get Current TDMS Reference.vi"

This can cause issues when you have multiple Size TDMS.lvclass instances in use for a project, since you might only end up with 1 clone instance of the "Get Current TDMS Reference.vi" and not check flush frequency or file size as often as the 5 second hardcoded default is intended.

This vi-based memory (shift register or feedback node) needs to be replaced with class private data so each instance of the class can maintain it's own last time check and last flush buffer check timestamp

Comments

Brian Hoover Yes I see the issue. Version 2.2.0.11 tries to address this. I created a private data type in the parent class for timer checking. It is just a scalar data in the class, so if you treated it like a reference, the data won't keep track of the last time the tick was checked. I think this is fine since it is really just a performance improvement and if you did split the wire it would be fine. It probably should have been a DVR. For the Time class I did put the last flush as part of the DVR.
 •  Reply • 1 year

Please sign in to leave a comment.