I asked a question recently about deadlocks in 100.7.
Michael Branscomb answered my question and I upgraded to 100.8
That upgrade made my experience much better, but as our testers have used it more, deadlocks are still occurring.
The callstacks are a little different than what I had seen in 100.7.
I have attached a txt file with the callstack details.
In the minidump I got from him, there are 45 threads waiting at mtx_do_lock.
The summary of threads is:
The second attachment, "100.8.hang2.txt" is an example when I was debugging.
The summary is:
Can you provide more information regarding:
- The system/environment (ideally a dxdiag report from 2-3 machines on which you are able to reproduce the issue you are seeing)
- What your application is doing at the time of the hang (if you are able to ascertain that) (e.g. user zoomed in)
- The composition of the map in terms of basemap layers (e.g. vector tiled layer), operational layers (e.g. feature layers from service feature table), and graphics overlays.
- Any specific UI interactions you have running e.g. identify on mouse move.
If you're not able to share here - please email firstname.lastname@example.org.