> Sometimes right after load and the first update of aircraft positions, > sometimes later I get: > > A script on this page may be busy, or it may have stopped responding. > You can stop the script now, open the script in the debugger, or let > the script continue.
Yup, I can get that too. What would happen if your map is still processing the last batch of data when the setimeout expires and calls for the next batch? That may happen in some circumstances, the way your update() function is structured, it kicks off a GDownloadUrl and then sets the timeout for the next. There's no guarantee that'll complete before the timeout. Suggestion ; set the timeout at the end of parseData() to be sure of sequencing properly. The page might go to sleep if any data request is never honoured, so you could also enhance with some other much longer timeout that would invoke a recovery action. > > http://maps.google.com/intl/en_ALL/mapfiles/150c/maps2.api/main.js:137 > > sometimes other line numbers are reported > > http://maps.google.com/intl/de_ALL/mapfiles/150c/maps2.api/main.js:656http://maps.google.com/intl/de_ALL/mapfiles/150c/maps2.api/main.js:170http://maps.google.com/intl/de_ALL/mapfiles/150c/maps2.api/main.js:420 > > It is not a browser-specific issue since it happens on Mac and > Windows, from IE6 over Firefox to Safari :( > > Did anything change on the google maps2 api during the last days that > could cause those errors? > > Any hints on how to debug this google stuff? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Maps API" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/Google-Maps-API?hl=en -~----------~----~----~----~------~----~------~--~---
