<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Deadlock in 100.8 in .NET Maps SDK Questions</title>
    <link>https://community.esri.com/t5/net-maps-sdk-questions/deadlock-in-100-8/m-p/119113#M1321</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I asked a question recently about deadlocks in 100.7.&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.esri.com/migrated-users/4061"&gt;Michael Branscomb&lt;/A&gt;‌ answered my question and I upgraded to 100.8&lt;/P&gt;&lt;P&gt;That upgrade made my experience much better, but as our testers have used it more, deadlocks are still occurring.&lt;/P&gt;&lt;P&gt;The callstacks are a little different than what I had seen in 100.7.&lt;/P&gt;&lt;P&gt;I have attached a txt file with the callstack details.&lt;/P&gt;&lt;P&gt;In the minidump I got from him, there are 45 threads waiting at mtx_do_lock.&lt;/P&gt;&lt;P&gt;The summary of threads is:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Esri_runtimecore::Geo_views::Map_view::set_viewpoint_&lt;/LI&gt;&lt;LI&gt;Esri_runtimecore::Map_renderer::Canvas_drawable::highlight_color&lt;UL&gt;&lt;LI&gt;from addlayer&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;LI&gt;Esri_runtimecore::Map_renderer::Map::copy_display_properties(void)&lt;UL&gt;&lt;LI&gt;from CoreGeoView.Pulse&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;LI&gt;Esri_runtimecore::Geo_views::Geo_view::update_attribution_(void)&lt;UL&gt;&lt;LI&gt;There are a lot of threads with this same callstack.&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The second attachment, "100.8.hang2.txt" is an example when I was debugging.&lt;/P&gt;&lt;P&gt;The summary is:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Esri_runtimecore::Geo_views::Map_view::set_view_insets_&lt;UL&gt;&lt;LI&gt;on the main/dispatcher thread&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;LI&gt;Esri_runtimecore::Geo_views::Geo_view::update_attribution_&lt;UL&gt;&lt;LI&gt;2 threads with this callstack this time.&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;LI&gt;Esri_runtimecore::Map_renderer::Canvas_drawable::highlight_color&lt;BR /&gt;&lt;UL&gt;&lt;LI&gt;from addlayer&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;LI&gt;Esri_runtimecore::Map_renderer::Map::copy_display_properties&lt;UL&gt;&lt;LI&gt;from CoreGeoView.Pulse&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Any ideas?&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Matt&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 01 Jul 2020 21:10:11 GMT</pubDate>
    <dc:creator>MattRickard</dc:creator>
    <dc:date>2020-07-01T21:10:11Z</dc:date>
    <item>
      <title>Deadlock in 100.8</title>
      <link>https://community.esri.com/t5/net-maps-sdk-questions/deadlock-in-100-8/m-p/119113#M1321</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I asked a question recently about deadlocks in 100.7.&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.esri.com/migrated-users/4061"&gt;Michael Branscomb&lt;/A&gt;‌ answered my question and I upgraded to 100.8&lt;/P&gt;&lt;P&gt;That upgrade made my experience much better, but as our testers have used it more, deadlocks are still occurring.&lt;/P&gt;&lt;P&gt;The callstacks are a little different than what I had seen in 100.7.&lt;/P&gt;&lt;P&gt;I have attached a txt file with the callstack details.&lt;/P&gt;&lt;P&gt;In the minidump I got from him, there are 45 threads waiting at mtx_do_lock.&lt;/P&gt;&lt;P&gt;The summary of threads is:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Esri_runtimecore::Geo_views::Map_view::set_viewpoint_&lt;/LI&gt;&lt;LI&gt;Esri_runtimecore::Map_renderer::Canvas_drawable::highlight_color&lt;UL&gt;&lt;LI&gt;from addlayer&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;LI&gt;Esri_runtimecore::Map_renderer::Map::copy_display_properties(void)&lt;UL&gt;&lt;LI&gt;from CoreGeoView.Pulse&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;LI&gt;Esri_runtimecore::Geo_views::Geo_view::update_attribution_(void)&lt;UL&gt;&lt;LI&gt;There are a lot of threads with this same callstack.&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The second attachment, "100.8.hang2.txt" is an example when I was debugging.&lt;/P&gt;&lt;P&gt;The summary is:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Esri_runtimecore::Geo_views::Map_view::set_view_insets_&lt;UL&gt;&lt;LI&gt;on the main/dispatcher thread&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;LI&gt;Esri_runtimecore::Geo_views::Geo_view::update_attribution_&lt;UL&gt;&lt;LI&gt;2 threads with this callstack this time.&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;LI&gt;Esri_runtimecore::Map_renderer::Canvas_drawable::highlight_color&lt;BR /&gt;&lt;UL&gt;&lt;LI&gt;from addlayer&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;LI&gt;Esri_runtimecore::Map_renderer::Map::copy_display_properties&lt;UL&gt;&lt;LI&gt;from CoreGeoView.Pulse&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Any ideas?&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Matt&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 01 Jul 2020 21:10:11 GMT</pubDate>
      <guid>https://community.esri.com/t5/net-maps-sdk-questions/deadlock-in-100-8/m-p/119113#M1321</guid>
      <dc:creator>MattRickard</dc:creator>
      <dc:date>2020-07-01T21:10:11Z</dc:date>
    </item>
    <item>
      <title>Re: Deadlock in 100.8</title>
      <link>https://community.esri.com/t5/net-maps-sdk-questions/deadlock-in-100-8/m-p/119114#M1322</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Any feedback on this &lt;A href="https://community.esri.com/migrated-users/4061"&gt;Michael Branscomb&lt;/A&gt;‌?&amp;nbsp; This is becoming a more prevalent issue with our user base.&lt;/P&gt;&lt;P&gt;FYI, we are doing some off-screen rendering of a map for printing, as recommended by &lt;A href="https://community.esri.com/migrated-users/3753"&gt;Rex Hansen&lt;/A&gt;.&lt;/P&gt;&lt;P&gt;This may be contributing to the problem, but certainly not the sole cause.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 16 Jul 2020 14:06:05 GMT</pubDate>
      <guid>https://community.esri.com/t5/net-maps-sdk-questions/deadlock-in-100-8/m-p/119114#M1322</guid>
      <dc:creator>MattRickard</dc:creator>
      <dc:date>2020-07-16T14:06:05Z</dc:date>
    </item>
    <item>
      <title>Re: Deadlock in 100.8</title>
      <link>https://community.esri.com/t5/net-maps-sdk-questions/deadlock-in-100-8/m-p/119115#M1323</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can you provide more information regarding:&lt;/P&gt;&lt;P&gt;- The system/environment (ideally a dxdiag report from 2-3 machines on which you are able to reproduce the issue you are seeing)&lt;/P&gt;&lt;P&gt;- What your application is doing at the time of the hang (if you are able to ascertain that) (e.g. user zoomed in)&lt;/P&gt;&lt;P&gt;- 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.&lt;/P&gt;&lt;P&gt;- Any specific UI interactions you have running e.g. identify on mouse move.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you're not able to share here - please email mbranscomb@esri.com.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Mike&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 16 Aug 2020 17:10:27 GMT</pubDate>
      <guid>https://community.esri.com/t5/net-maps-sdk-questions/deadlock-in-100-8/m-p/119115#M1323</guid>
      <dc:creator>MichaelBranscomb</dc:creator>
      <dc:date>2020-08-16T17:10:27Z</dc:date>
    </item>
  </channel>
</rss>

