Inconsistent weirdness with llMapDestination

If I call llMapDestination(region, coord, ZERO_VECTOR) with region set to the appropriate region, and coord set to the destination coordinates in that region, I get an inconsistent (unpredictable) result when the map comes up. About two thirds of the time, the map comes up with the right location highlighted. About one third of the time it come up with the right region but the coordinates are close to my present location and not the coordinates that I passed. For example if I am at Gurshi (16, 124, 60) and I want to go to Bear (31,131,11), the map comes up to Bear (17, 125, 60).

I know that coord is set correctly because I output it in a llOwnerSay right before the call to llMapDestination. I tried introducing a llSleep(0.05) right before the llMapDestination call but that does not seem to do anything.

What gives? Is this a bug? Am I doing something wrong? Is there a workaround to make this work as intended.

Sorry. I should have checked the Jira first. This is bug VWR-2060 (since Aug 2007). So far the fix for me is to call llMapDestination twice in immediate succession. The first call uses coordinates <128,128,100>, the second uses the correct coordinates. Only one map comes up, first to the <128,128,100> coordinates and a hiccup later to the correct coordinates.

good to know, I hadn't gotten an off results yet that I can remember, but I'm using a slightly different method

I've been feeding world coordinates to llMapDestination, via requestInventoryData on a landmark, and setting the region name to the current region... the map pops up with my current region shown, and my destination highlighted...(similar to pushing the show my location button)

whether it's specifying my current region for the view center, or using world coordinates that prevents the bug, I don't know... but it'd be something to test and add to the jira article, I'm adding a watch on this article.