An infinite loop caused by ajaxComplete?

ajaxComplete calls fetchResults causes ajaxComplete causes fetchResults....

IIS applicationPool MaxConcurrentRequestsPerCPU ?

ajaxComplete triggers fetchResults which in turn triggers ajaxComplete

Each and every ajax call will trigger an ajaxComplete, which will trigger an ajax get, which will trigger an ajaxComplete, which will trigger an ajax get, which etc etc ... ;)

// Ryan

Kudos ayende for not misusing your position with regard of having the keenest and fastest bug finders.

PS I regularly must reload your captchas because they are hard. I am staring at what seems to be hebrew...

I just happened to have Fiddler and this blog open on the day this happened. I saw the madness for myself. Hilarity ensued.

ajaxComplete -> fetchResults -> ajaxComplete etc.

Even on a Friday, after a drink I spotted that one.

I assume that the real scenario was not as clearly presented.

More hard things please. ;-)

It would have worked if the profiler itself did not return X-RavenDb-Profiling-Id. Unless the profiler markup / js also needs this

I'm tempted to say stuff like "idiotic", "stupid" and "wtf?!". But I'm not going to.

I assume the fix is :-

if (!id) fetchresults(id.split(', '));