IE Stack Overflow at location 0

In-depth analysis

http://cappuccino.org/discuss/2010/03/01/internet-explorer-global-variables-and-stack-overflows/
http://www.nczonline.net/blog/2009/05/19/javascript-stack-overflow-error/
http://stackoverflow.com/questions/1288962/ie8-native-json-parse-bug-causes-stack-overflow

Need to use settimeout ?

http://creatorish.com/weblog/323
https://github.com/stamen/modestmaps-js/commit/c202b0a274f4235c4ebd8362fff11d88a2c0fc8f

Stack trace tool

https://github.com/eriwen/javascript-stacktrace
http://web.archive.org/web/20100813232637/http://blog.yoursway.com/2009/07/3-painful-ways-to-obtain-stack-trace-in.html
http://stackoverflow.com/questions/1502765/javascript-stack-trace-in-ie-or-maybe-just-a-simple-javascript-error

ASP.NET background thread

http://haacked.com/archive/2011/10/16/the-dangers-of-implementing-recurring-background-tasks-in-asp-net.aspx

http://blogs.msdn.com/b/tmarq/archive/2010/04/14/performing-asynchronous-work-or-tasks-in-asp-net-applications.aspx

In v4.0 ASP.NET, we won’t unload the AppDomain until all requests have completed. In v2.0/3.5 ASP.NET in IIS 7 integrated mode, we also won’t unload the AppDomain until all the requests have completed.  In v2.0/3.5 classic mode, we will only wait until httpRuntime/shutdownTimeout has been exceeded before unloading the AppDomain, so long running async requests are vulnerable to being rudely aborted.  To work around this, you’d want the shutdownTimeout to be sufficiently long.