nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

JavaScript API website and Chrome memory issue

TomSellsted

Anybody having issues with large amounts of memory being used when looking at the ArcGIS API for JavaScript website using a Chrome browser? If I camp on that website, Chrome starts just using up lots of my systems memory. It takes a while though. This morning when I came in, it had allocated 2.8Gb of memory. As soon as I dismiss the tab, the memory is reallocated. Very weird... The same happens on the ArcGIS API for Flex too.

Trouver plus de publications taguées avec

Accepted answers

rscheitlin

Tom,

I can confirm the same (no longer having memory issues).

All comments

TomSellsted

Robert,

Just checking back with you. Were you able to duplicate this problem?

Thanks very much!

Regards,

Tom

TomSellsted

Here is the task manager arriving at work today...

Here is the task manager after dismissing the JavaScript API website tab.

TomSellsted

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.

rscheitlin

Tom,

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.

TomSellsted

Robert,

Thanks for the speedy response. This is not an app that I developed. It is just browsing to the ArcGIS API for JavaScript website. Other browsers don't gobble up memory, but Chrome does.

Just navigate to: ArcGIS API for JavaScript using Chrome and open up the Task Manager. It takes a couple of hours, but it will start building up a large use of memory.

I use the API reference page a lot so I generally just camp on this website all day.

Thanks!

Best Regards,

Tom

rscheitlin

Tom,

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.

Rejoindre la conversation

Les membres connectés peuvent publier, suivre les mises à jour, et plus encore. Nouveau ici ? Inscrivez-vous gratuitement.

Liens rapides

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.