I have encountered an issue with Alarm management.
A simple Alarm table to display active alarms. Historical alarms can be hidden and can also be cleared. Overall a history of 10000 alarms before it cycles.

On one instance this error displayed:
"Some kind of disk I/O error ocurred. Check disk space". Picture attached.

I have seen this with an online change, but it was resolved by a full download. But this case was running for weeks and displaying alarms fine. The logged errors though were unusual.

Associated log entries (multiples of these were logged):

2026-10-07T12:17:17.603Z, 0x0000001f, 8, 1, 0, #### Exception: Memory double free detected: <cmp>AlarmConfig</cmp> <addr>0x80330d0</addr>

And later in the same day, the entire application encountered an exception:

2026-10-07T19:33:48.583Z, 0x00000011, 8, 81, 3, #### Exception: *EXCEPTION* [<excpt>AccessViolation</excpt>] occurred: App=[<app>Application</app>], T>
2026-10-07T19:33:48.583Z, 0x00000011, 8, 81, 3, #### Exception: *SOURCEPOSITION* App=[<app>Application</app>] area=<area>0</area>, offset=<off>9548256>

I haven't found any explanation for a "Memory double free detected" and I'm unsure how to prevent it occurring. I suspect it might be the cause of the "Access Violation" exception, but how can I be sure of this?

Would defining VISU_NO_EXCEPTION_HANDLING be advisable or not in a production environment?

Any advice is welcome.