Bryant Likes's Blog

Thanks man! great post!

Honestly I was heading to the gun store to end it all when I found this. My children thank you...

Thanks man i was about to shoot my colleague for crashing my 3 days of hard work :)

This is an incredible bug.  I'm just glad that several people have this issue posted on their blogs like you do!!  There is probably a hotfix for this one...but if there is, it's probably only available to huge corporations that demand Microsoft give it to them.  That's how I've always heard these little problems get fixed anyway.  It's too bad for the rest of us.

Thanks a million. This bug was driving me crazy, until I found your blog!!!

Upon first reading this I thought I had found the solution to my problem.  I went and changed all my counter variables from i's to j's, fired it up and doh... same error.  Upon clicking on the hyperlinked "turns out" text above, the problem can occur even if the variable scoping issues are addressed, particularly when several callbacks are made in quick succession.  I haven't found a clean/simple solution to this issue yet.  FWIW I'm using the setTimeout(expression, delay) method for now and it seems to have gotten rid of this blasted error.

I have the same error in my application where i used callback event handler where i continously calling

callback event after a period of time to get the new data from database on the basis of passed property id as a argument.

so that how can i change this temporary internet file(webresource.axd)? to run my application by make the for loop like this

for (i = 0; i < __pendingCallbacks.length; i++) {...}

with:

for (var i = 0; i < __pendingCallbacks.length; i++) {...}

Please let me know the solution of this problem

Thanks

Thank you!

It's so simple, but fix a lot of probleams!

I replaced each 'i' on my page per 'p'. And it stops the probleam!

Thanks.

Thanks a Ton!! i would have gone mad, had this posting not been there.

Thanks a lot, I was going nuts, this really solved my issue

Just what I needed Thanks.

thanks!!! Worked like a charm.

Thank you!!!.. i havenot tried the soln..but hope this will help...I was only one step away from depression!!

God Damn Microsoft. And they wonder why their stuff is crap. When i look at the javascript code for their callback feature, it looks like it was just slapped together and it worked sometimes, and that was good enough for them! I can't believe this crap came from them.

Thsnk you, I abandoned a page because of this some time ago, this time i was determend to work it out, i luckily found your page straight away.

What will happen when you call an Asyncronous method inside a loop? I did a small experiment to find

kudos!!! this not only solved my problem but also i got something new to learn about the variable i which is declared. Thanks a ton!!!

Thanx a lot, it solved my problem really

Thank you, it was excelent solution

Thanx you, a was really fed up with this error.

Thanks alot for this find. I overlooked their missing declaration and couldnt explain how i was suddenly 5 although it should have been 0.

Good job!

I didn't have any javascript method which uses variable i. Still I am getting this error. So made a small change to my .cs

public void RaiseCallbackEvent(string eventArgument) {

       .....

//just added this line and now not getting the javascript error.

       System.Threading.Thread.Sleep(500);    

}

This may help!

You will see this same crash with recursive callbacks; i.e. if your script makes a call to the server from within a callback handler

Thank you only replaced the 'i' variable's name for another... Really thank you!!

Thank you!

I need to join everyone in thanking you for this post. You just saved me days of searching!!!

"You will see this same crash with recursive callbacks; i.e. if your script makes a call to the server from within a callback handler"

^^^ How do you get around this? The problem is I am calling it from an onchange event handler on one control, then on the call back handler i need to fire the onchange event on the second control.

You can get around the error when recursively calling another callback inside a callback handler by delaying the call using window.setTimeout.

example:

BEFORE

function MyCallbackHandler(arg,context) {

 WebForm_DoCallback(......);

}

AFTER

function MyCallbackHandler(arg,context) {

 window.setTimeout("WebForm_DoCallback(......);",0);

}

Thank you , it's excelent solution!

Woo :)

Thank you VERY much. I am calling a callback from a (devexpress) grid callback handler and was having the exact problem. Hopefully this works!

Hey it didnt work for me.

what may be there I replaced all

variables i with ddItemCounter

but still get the same error.

Any more idea???

Lots of thanks!!

Cthulhu f'thang

Thanks for this post.

Thanks a lot solution dear. Really thanks

THANK YOU!!!  Your solution made my day!

Unbelieveable... thanks for the solution!!!

I can't believe this is still an error in the framework! Thanks!

THANK YOU!!!  I've been debugging this problem for hours.