Summary
The Verse runtime occasionally terminates execution with the error ErrRuntime_InfiniteLoop, even though the code does not contain any infinite loops. The issue happens randomly and, when it occurs, it generates a large batch of errors at once (hundreds). Logs provide no callstack, making debugging difficult. The error may be misleading, as it could be caused by something other than an actual infinite loop.
Please select what you are reporting on:
Verse
What Type of Bug are you experiencing?
Verse
Steps to Reproduce
It is not possible to reproduce consistently. The error occurs randomly. When it happens, it appears in large batches at once (hundreds of occurrences), without any specific action triggering it.
The issue was detected in two different maps, both sharing the same code.
All implemented loops contain either sleep statements or exit conditions (break).
There are no loops that run indefinitely.
The log does not provide a callstack, only the generic infinite loop message.
Expected result
The code should run normally without the runtime terminating due to a supposed infinite loop.
Expected Result
The runtime stops execution with the error infinite loop (ErrRuntime_InfiniteLoop), even though no actual infinite loops exist in the code.
The issue is not frequent, but when it occurs, it results in a large number of accumulated errors.
Example:
08/19/2025 (around 10 PM): 131 errors logged.
08/20/2025: new errors occurred, bringing the total to 326 errors.
The problem may be misleading: the system reports it as an infinite loop, but the underlying cause could be different.
Observed Result
The code should execute without interruption, and the Verse runtime should not terminate due to a false detection of an infinite loop.
Loops that contain sleep or break should be handled as valid and not flagged as infinite.
No unexpected runtime termination should occur, and the system should provide a proper callstack if an actual error happens.
Platform(s)
PC
Island Code
3012-4027-0050