New Post: Potential Stackoverflow on Azure Web Apps

Hi

Thanks for the prompt reply. We used to get the error occurring in various execution paths but after upgrades and refinements (such as tuning the reuse of runtimes and engines, invoking garbage collection, precompiling scripts) it has narrowed down to one scenario/piece of code:

(typeof _myVariable !== 'undefined')

This will have been run before every execution of javascript code across all our requests hence the fact that it's seemingly random given it only happens once in a while. We could indeed try...catch and retry or even dispose the engine and initialise a new one but only want to do that as a last resort (e.g. if that's the nature of the v8 engine). Other options could be to change the above code if it's causing the condition within v8... but it all seems very odd as we've only ever seen it on azure apart from when i artificially created it by setting the stack usage limit to a low figure - otherwise we don't set stack usage limits.

Thanks once again.
James