PanEvent.PAN_END event being generated repeatedly even though map is not being panned

Question

We are encountering a strange problem after zooming in/out a lot when the map is around London, England. The event listener for PanEvent.PAN_END is being called repeatedly even though the map is not being panned. Greenwich in SE London (and the prime meridian) are within the map boundaries for some of the maps and outside for others (depending on the scale / zoom level). In the call stack we can see that the enterFrameHandler function is called and that it calls dispatchPanEnd. Is there any scenario in which the dispatchPanEnd would be called repeatedly (every second or two), because that's what we're seeing when the problem occurs. We have not been able to reproduce the problem in the US, which makes us suspect some kind of issue at the prime meridian. The impact on the application is that it gets unresponsive as its trying to keep up with the onslaught of requests made every second or so. Do you have any recommendations for a workaround on our end? We are not really in a position to upgrade to a later version of the ESRI Flex API at this time. We are using a base map with no other layers. Interestingly, after the onslaught begins, if we stop the FlexViewer app and restart it (which brings up the map at the same extents as last time), the requests start up again. Note that we do change the map's extent to a user-defined envelope after the initial map load. We are using 2.4 version of ESRI Flex API.

DasaPaddock · Answer

Did you mean to call arcgistiledmapservicelayer1_loadHandler() on the updateEnd event? This is causing the loop since it's continually resetting the map's extent. If you call this on the layer's "load" event instead, it will only be called once.

TerryCampbell · Answer

Tried with 2.5 API and issue still occurred. Commented out the code to change the map's extent to a user-defined envelope after the initial map load. World map came up initially. Zoomed into London area and was able to reproduce problem. Created a sample app and got different results. With the code below, it brought up map with first extents, then switched to second set of extents then repeatedly got into map1_panEndHandler. We found that it didn't matter where the 2 sets of extents were. So, this is not the same as the problem originally reported, but could be related. It seems to be a situation where a pan end handler gets called repeatedly in an infinite loop. Any idea why?

DasaPaddock · Answer

Can you try the 2.5 API?

Have you tried without the code for "Note that we do change the map's extent to a user-defined envelope after the initial map load."?

Can you share this code?