Hang/Deadlock in CoreGeoView.Pulse

MattRickard

I am occasionally getting a deadlock in CoreGeoView.Pulse.

I am using 100.7 currently.

My map has about 100 FeatureLayers from an mmpk.

I do have multiple maps within the same application as well.

If my code does something at just the wrong time, it hangs.

Here are the activities I am doing that may cause it:

• Add/Remove Layers
• SetViewpoint
  • We are calling this frequently, using our own navigation mechanism.
• Set Feature Visibility on certain FeatureLayers

Are there any known issues with CoreGeoView.Pulse getting stuck for an extended period of time, or getting interrupted and deadlocking?

Is there any status I can check to see if the map is ready.

We are checking for MapView.Loaded, Map.LoadStatus.

We also tried to monitor DrawStatus, but delaying activity until the map is fully drawn isn't the best user experience.

MattRickard

Upgrading to 100.8 seems to have helped quite a bit.

I also rearranged my code to not rapidly:

• add layers
• set viewpoint
• set Feature visibility

I'll submit another question about the visual quality issues I am seeing.

Thanks for the help.