Hi James,
Interesting. Are you saying that the JavaScript expression above is somehow responsible for the issues you're seeing?
In any case,
Consider also that true stack overflows aren't uncommon. ClearScript can build up large stacks, especially with nested script execution, and the default stack allocation is typically only 1 MB.
Cheers!
Interesting. Are you saying that the JavaScript expression above is somehow responsible for the issues you're seeing?
In any case,
try..catch might be a low-cost way to diagnose the problem. It won't catch true stack overflows, but it should be able to find cases of empty strings (or similar objects) being thrown, and it shouldn't affect your application's performance.Consider also that true stack overflows aren't uncommon. ClearScript can build up large stacks, especially with nested script execution, and the default stack allocation is typically only 1 MB.
Cheers!