<?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 JavaScript API website and Chrome memory issue in ArcGIS JavaScript Maps SDK Questions</title>
    <link>https://community.esri.com/t5/arcgis-javascript-maps-sdk-questions/javascript-api-website-and-chrome-memory-issue/m-p/753173#M69625</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Anybody having issues with large amounts of memory being used when looking at the ArcGIS API for JavaScript website using a Chrome browser?&amp;nbsp; If I camp on that website, Chrome starts just using up lots of my systems memory.&amp;nbsp; It takes a while though.&amp;nbsp; This morning when I came in, it had allocated 2.8Gb of memory.&amp;nbsp; As soon as I dismiss the tab, the memory is reallocated.&amp;nbsp; Very weird...&amp;nbsp; The same happens on the ArcGIS API for Flex too.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 13 Nov 2014 16:12:36 GMT</pubDate>
    <dc:creator>TomSellsted</dc:creator>
    <dc:date>2014-11-13T16:12:36Z</dc:date>
    <item>
      <title>JavaScript API website and Chrome memory issue</title>
      <link>https://community.esri.com/t5/arcgis-javascript-maps-sdk-questions/javascript-api-website-and-chrome-memory-issue/m-p/753173#M69625</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Anybody having issues with large amounts of memory being used when looking at the ArcGIS API for JavaScript website using a Chrome browser?&amp;nbsp; If I camp on that website, Chrome starts just using up lots of my systems memory.&amp;nbsp; It takes a while though.&amp;nbsp; This morning when I came in, it had allocated 2.8Gb of memory.&amp;nbsp; As soon as I dismiss the tab, the memory is reallocated.&amp;nbsp; Very weird...&amp;nbsp; The same happens on the ArcGIS API for Flex too.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 13 Nov 2014 16:12:36 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-javascript-maps-sdk-questions/javascript-api-website-and-chrome-memory-issue/m-p/753173#M69625</guid>
      <dc:creator>TomSellsted</dc:creator>
      <dc:date>2014-11-13T16:12:36Z</dc:date>
    </item>
    <item>
      <title>Re: JavaScript API website and Chrome memory issue</title>
      <link>https://community.esri.com/t5/arcgis-javascript-maps-sdk-questions/javascript-api-website-and-chrome-memory-issue/m-p/753174#M69626</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Tom,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp; Is it unique to your web app that you developed? I sounds like you have some code that is continually creating a new object (like in a loop or timeout) and never destroying it or setting it to null.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 13 Nov 2014 16:27:19 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-javascript-maps-sdk-questions/javascript-api-website-and-chrome-memory-issue/m-p/753174#M69626</guid>
      <dc:creator>RobertScheitlin__GISP</dc:creator>
      <dc:date>2014-11-13T16:27:19Z</dc:date>
    </item>
    <item>
      <title>Re: JavaScript API website and Chrome memory issue</title>
      <link>https://community.esri.com/t5/arcgis-javascript-maps-sdk-questions/javascript-api-website-and-chrome-memory-issue/m-p/753175#M69627</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Robert,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for the speedy response.&amp;nbsp; This is not an app that I developed.&amp;nbsp; It is just browsing to the ArcGIS API for JavaScript website.&amp;nbsp; Other browsers don't gobble up memory, but Chrome does.&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Just navigate to: &lt;A href="https://developers.arcgis.com/javascript/" title="https://developers.arcgis.com/javascript/"&gt;ArcGIS API for JavaScript&lt;/A&gt; using Chrome and open up the Task Manager.&amp;nbsp; It takes a couple of hours, but it will start building up a large use of memory.&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I use the API reference page a lot so I generally just camp on this website all day.&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;Best Regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Tom&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 13 Nov 2014 16:43:58 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-javascript-maps-sdk-questions/javascript-api-website-and-chrome-memory-issue/m-p/753175#M69627</guid>
      <dc:creator>TomSellsted</dc:creator>
      <dc:date>2014-11-13T16:43:58Z</dc:date>
    </item>
    <item>
      <title>Re: JavaScript API website and Chrome memory issue</title>
      <link>https://community.esri.com/t5/arcgis-javascript-maps-sdk-questions/javascript-api-website-and-chrome-memory-issue/m-p/753176#M69628</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Tom,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; OK. Firefox is my primary browser and the one I leave the resources pages open with for multiple days. I will test this with Chrome and see if I can duplicate your findings.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 13 Nov 2014 17:01:26 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-javascript-maps-sdk-questions/javascript-api-website-and-chrome-memory-issue/m-p/753176#M69628</guid>
      <dc:creator>RobertScheitlin__GISP</dc:creator>
      <dc:date>2014-11-13T17:01:26Z</dc:date>
    </item>
    <item>
      <title>Re: JavaScript API website and Chrome memory issue</title>
      <link>https://community.esri.com/t5/arcgis-javascript-maps-sdk-questions/javascript-api-website-and-chrome-memory-issue/m-p/753177#M69629</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have had a tab open to the JavaScript API web site most of the day and it has over a gigabyte of memory consumed.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 13 Nov 2014 23:59:02 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-javascript-maps-sdk-questions/javascript-api-website-and-chrome-memory-issue/m-p/753177#M69629</guid>
      <dc:creator>TomSellsted</dc:creator>
      <dc:date>2014-11-13T23:59:02Z</dc:date>
    </item>
    <item>
      <title>Re: JavaScript API website and Chrome memory issue</title>
      <link>https://community.esri.com/t5/arcgis-javascript-maps-sdk-questions/javascript-api-website-and-chrome-memory-issue/m-p/753178#M69630</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Here is the task manager arriving at work today...&lt;/P&gt;&lt;P&gt;&lt;IMG alt="tmbefore.png" class="jive-image image-1" src="https://community.esri.com/legacyfs/online/29887_tmbefore.png" style="width: 620px; height: 395px;" /&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Here is the task manager after dismissing the JavaScript API website tab.&lt;/P&gt;&lt;P&gt;&lt;IMG alt="tmafter.png" class="jive-image image-2" src="https://community.esri.com/legacyfs/online/30074_tmafter.png" style="width: 620px; height: 395px;" /&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 14 Nov 2014 16:13:31 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-javascript-maps-sdk-questions/javascript-api-website-and-chrome-memory-issue/m-p/753178#M69630</guid>
      <dc:creator>TomSellsted</dc:creator>
      <dc:date>2014-11-14T16:13:31Z</dc:date>
    </item>
    <item>
      <title>Re: JavaScript API website and Chrome memory issue</title>
      <link>https://community.esri.com/t5/arcgis-javascript-maps-sdk-questions/javascript-api-website-and-chrome-memory-issue/m-p/753179#M69631</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Robert,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Just checking back with you.&amp;nbsp; Were you able to duplicate this problem?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks very much!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Tom&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 18 Nov 2014 16:34:58 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-javascript-maps-sdk-questions/javascript-api-website-and-chrome-memory-issue/m-p/753179#M69631</guid>
      <dc:creator>TomSellsted</dc:creator>
      <dc:date>2014-11-18T16:34:58Z</dc:date>
    </item>
    <item>
      <title>Re: JavaScript API website and Chrome memory issue</title>
      <link>https://community.esri.com/t5/arcgis-javascript-maps-sdk-questions/javascript-api-website-and-chrome-memory-issue/m-p/753180#M69632</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Tom,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; Yes. I can have Chrome open to the JS API Resource page and just watch the memory climb in Task Manager every couple of seconds.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 18 Nov 2014 16:56:21 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-javascript-maps-sdk-questions/javascript-api-website-and-chrome-memory-issue/m-p/753180#M69632</guid>
      <dc:creator>RobertScheitlin__GISP</dc:creator>
      <dc:date>2014-11-18T16:56:21Z</dc:date>
    </item>
    <item>
      <title>Re: JavaScript API website and Chrome memory issue</title>
      <link>https://community.esri.com/t5/arcgis-javascript-maps-sdk-questions/javascript-api-website-and-chrome-memory-issue/m-p/753181#M69633</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thank you sir!&amp;nbsp; I am not exactly sure who to report this problem to.&amp;nbsp; I was hoping that someone from ESRI would see this post and investigate.&amp;nbsp; I have inadvertently left my Chrome browser open to this page overnight and had my system run out of memory.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Tom &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 18 Nov 2014 17:05:20 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-javascript-maps-sdk-questions/javascript-api-website-and-chrome-memory-issue/m-p/753181#M69633</guid>
      <dc:creator>TomSellsted</dc:creator>
      <dc:date>2014-11-18T17:05:20Z</dc:date>
    </item>
    <item>
      <title>Re: JavaScript API website and Chrome memory issue</title>
      <link>https://community.esri.com/t5/arcgis-javascript-maps-sdk-questions/javascript-api-website-and-chrome-memory-issue/m-p/753182#M69634</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Tom,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; Let me tag a couple of JS API people&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.esri.com/migrated-users/2525"&gt;Kelly Hutchins&lt;/A&gt;‌&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.esri.com/migrated-users/37892"&gt;Jonathan Uihlein&lt;/A&gt;‌&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 18 Nov 2014 17:18:39 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-javascript-maps-sdk-questions/javascript-api-website-and-chrome-memory-issue/m-p/753182#M69634</guid>
      <dc:creator>RobertScheitlin__GISP</dc:creator>
      <dc:date>2014-11-18T17:18:39Z</dc:date>
    </item>
    <item>
      <title>Re: JavaScript API website and Chrome memory issue</title>
      <link>https://community.esri.com/t5/arcgis-javascript-maps-sdk-questions/javascript-api-website-and-chrome-memory-issue/m-p/753183#M69635</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks very much Robert!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 18 Nov 2014 18:47:19 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-javascript-maps-sdk-questions/javascript-api-website-and-chrome-memory-issue/m-p/753183#M69635</guid>
      <dc:creator>TomSellsted</dc:creator>
      <dc:date>2014-11-18T18:47:19Z</dc:date>
    </item>
    <item>
      <title>Re: JavaScript API website and Chrome memory issue</title>
      <link>https://community.esri.com/t5/arcgis-javascript-maps-sdk-questions/javascript-api-website-and-chrome-memory-issue/m-p/753184#M69636</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks for reporting the memory issue.&amp;nbsp; This affects, some but not all of the pages on the developers site. We will look into it more.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 25 Nov 2014 01:35:07 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-javascript-maps-sdk-questions/javascript-api-website-and-chrome-memory-issue/m-p/753184#M69636</guid>
      <dc:creator>BjornSvensson</dc:creator>
      <dc:date>2014-11-25T01:35:07Z</dc:date>
    </item>
    <item>
      <title>Re: JavaScript API website and Chrome memory issue</title>
      <link>https://community.esri.com/t5/arcgis-javascript-maps-sdk-questions/javascript-api-website-and-chrome-memory-issue/m-p/753185#M69637</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Bjorn,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks very much for checking into this problem.&amp;nbsp; I can see an improvement already!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Tom&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 25 Nov 2014 16:20:25 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-javascript-maps-sdk-questions/javascript-api-website-and-chrome-memory-issue/m-p/753185#M69637</guid>
      <dc:creator>TomSellsted</dc:creator>
      <dc:date>2014-11-25T16:20:25Z</dc:date>
    </item>
    <item>
      <title>Re: JavaScript API website and Chrome memory issue</title>
      <link>https://community.esri.com/t5/arcgis-javascript-maps-sdk-questions/javascript-api-website-and-chrome-memory-issue/m-p/753186#M69638</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;FYI - it seems like this might have gotten fixed by Google fixing memory issues in the Chrome browser. It seems to be fine with version 39.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 25 Nov 2014 19:46:12 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-javascript-maps-sdk-questions/javascript-api-website-and-chrome-memory-issue/m-p/753186#M69638</guid>
      <dc:creator>BjornSvensson</dc:creator>
      <dc:date>2014-11-25T19:46:12Z</dc:date>
    </item>
    <item>
      <title>Re: JavaScript API website and Chrome memory issue</title>
      <link>https://community.esri.com/t5/arcgis-javascript-maps-sdk-questions/javascript-api-website-and-chrome-memory-issue/m-p/753187#M69639</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Bjorn,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have been using version 39 and there still was a problem.&amp;nbsp; It does appear that some modification was made though as I don't show any memory issues when viewing developer site pages today. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks again for getting back to me!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Tom&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 25 Nov 2014 20:10:48 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-javascript-maps-sdk-questions/javascript-api-website-and-chrome-memory-issue/m-p/753187#M69639</guid>
      <dc:creator>TomSellsted</dc:creator>
      <dc:date>2014-11-25T20:10:48Z</dc:date>
    </item>
    <item>
      <title>Re: JavaScript API website and Chrome memory issue</title>
      <link>https://community.esri.com/t5/arcgis-javascript-maps-sdk-questions/javascript-api-website-and-chrome-memory-issue/m-p/753188#M69640</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Tom,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; I can confirm the same (no longer having memory issues).&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 25 Nov 2014 20:28:13 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-javascript-maps-sdk-questions/javascript-api-website-and-chrome-memory-issue/m-p/753188#M69640</guid>
      <dc:creator>RobertScheitlin__GISP</dc:creator>
      <dc:date>2014-11-25T20:28:13Z</dc:date>
    </item>
  </channel>
</rss>

