More information for the crash related improvements in the latest version

[LeeYangLBLBCS]

Where can I find more information on the fixes on crashes you have described in the release notes?
For example:
Fixed crash of negative enums
Resolved a crash that occurred when enabling field values without field names enabled.

I am wondering if they would fix the crashes I'm experencing in the older caLab version. (3.x.x)

[nugatritter]

Thank you for your interest in the project.

All available details about changes, including crash fixes, are documented in the changelog. The entries you've referenced (e.g., "Fixed crash of negative enums") are summarized there based on the internal debugging and fixes applied.

If you're experiencing crashes with an older version (3.x.x), it's very likely that updating to the latest release will resolve at least some of them, especially if they match the descriptions in the changelog. However, without specific information about your crashes (e.g., error messages, stack traces, steps to reproduce), it's difficult to say with certainty.

If you're able to share more details about the crashes you're encountering, I'd be happy to take a closer look and help determine whether they're addressed in the current release.

[LeeYangLBLBCS]

I have experienced Labview crashes without warning, without error message. CALab is one of the suspicious components I'm suspecting is playing a role after some debugging.
Unfortunately we are using an older version Labview 2018. It is not compatible with the newer version CALab.
Therefore, I would like to understand what the details is about the crash fixes documented in the changelog.
For example, for this fix: Fixed crash of negative enums:
What does the "negative enums" mean, which would cause a crash? If I know what it means, I could try to change the code to avoid such siituation.
Thanks.

[nugatritter]

Hello Lee, Enumeration is an EPICS data type. It only recognizes positive integers. However, if a negative number is passed for writing for variables of this data type, then there was a crash in the old CA Lab version. Unfortunately, I won't be able to access a computer with LapVEW until May 7. Therefore my possibilities for support are very limited Best Carsten 20.04.2025 00:36:43 Lee Yang ***@***.***>:

…

[Bild]*LeeYangLBLBCS* left a comment (epics-extensions/CALab#26)[#26 (comment)] I have experienced Labview crashes without warning, without error message. CALab is one of the suspicious components I'm suspecting is playing a role after some debugging. Unfortunately we are using an older version Labview 2018. It is not compatible with the newer version CALab. Therefore, I would like to understand what the details is about the crash fixes documented in the changelog. For example, for this fix: Fixed crash of negative enums: What does the "negative enums" mean, which would cause a crash? If I know what it means, I could try to change the code to avoid such siituation. Thanks. — Reply to this email directly, view it on GitHub[#26 (comment)], or unsubscribe[https://github.com/notifications/unsubscribe-auth/AEDGVTM6SLT7XLXYWHXGRCL22LFXXAVCNFSM6AAAAAB3OUIWTKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQMJWHA4TCMRXGA]. You are receiving this because you commented.

[brian-stravaro]

It sounds like you are using CA Lab version 1.6.x. There have been several crash fixes in the last few years. In particular, if you are using LabVIEW events to monitor PVs, you should upgrade (and make sure to use the unregister VI in CA Lab 1.7.x).

There have also been several significant performance improvements if you are using hundreds or thousands of PVs.

If you need support for older versions of LabVIEW, I believe version 1.7.3.0 supported versions back to LabVIEW 8.5. You can download it from the Releases page on Github.