Just using 12S as my dev blog again...

So you have a method in your class that loads up some XML from the server, and it sets up an onLoad event handler to the parse the XML.

But now you want to cancel that load before it's finished. You cancel the timer you had running and you set that XML object to null - but it still seems that the onLoad handler is getting called and that's causing some odd results.

The solution is to make sure you delete the onLoad handler before you nullify that XML object.

proTip++

Unfortunately if you watch with Charles, your app is indeed still loading the data. There's just no object to receive the data with your solution.

It drives me nuts.

Your solution does stop those onloads from firing though which can be handy in recursive situations.

still it drives me nuts that you can't kill the request, especially when its a cancellation of a large file.