Not enough memory for ArcGIS Experience Builder web app

[williamsonsa_fultonhogan]

Hi,

We're currently building a web application with ArcGIS Experience Builder and beginning to encounter an issue where the users web browser crashes with the error "Not Enough Memory".

The Web Experience we are building comprises of 6 pages, and the majority of the pages includes a map accompanied by a data centric widget i.e. a list, feature info or edit widget. We've configured the maps on each page to synchronise their zoom extents, and we've also applied data filtering actions throughout the app. Additionally, one page consists of an embedded Survey123 form, which has 3 pages, with 2 related tables.

All in all, its a relatively complex app with a lot of content - but this is exactly why we want to use Experience Builder.

1. Are there any documented limitations to how much content, or how many 'actions' an experience can support?
2. Alternatively, is there a way to configure pages to unload when a user navigates away from the screen? it would be useful for the page with Survey123 embedded into it to unload when the user is finished with it to free up browser memory.

I can't share links or screenshots unfortunately.

Cheers,

Sam

[Lindsay]

Hey @williamsonsa_fultonhogan ,

I had issues running out of memory last week too. It was because I had a layer added in through a web service, but that's probably not your issue.

In regard to number 2, in the past I've had issues loading because I've had too many sections, some of which contained S123s, but then they added in the lazy load check box and that sorted things for me.

These are some small things that might help, but I'll keep an eye on your thread as I'm curious about this too.