There isn’t any debugging feature for that, at least not in construct. The browser’s debugger can let you look at the JavaScript where it’s looping, but that is very abstracted away from events so it probably isn’t very useful. I mean if we wanted to deal with JavaScript and debugging it we’d be using something other than construct.
Anyways,
You don’t have to check every loop you have though.
If you use “while”, then I’d pay attention to that. It’s the only way to create an infinite loop other than with function recursion.
Just make sure it can exit the loop. If not then as a band aid you could replace the while with a repeat. That way it will just stop instead of looping indefinitely.
The second thing to look out for isn’t an Infinite loop, but a loop that takes long enough that the browser asks to stop it. It happens with infinite loops too, but I digress.
Are you looping over big arrays that are increasing in size?
Do you have a loop that changes the number if iterations based on an expression that sometimes gives a very big number?
Anyways that’s where I’d look.
Ideas to mitigate that is to not loop over an entire giant array in one tick but do it in smaller chunks. Like half one frame and the other half the next. Big is the key word here.