I had an issue this morning with an Experience Builder app, and while it seems to have resolved, I'm still puzzled and wondering if anyone else has had a similar experience (or ideas in case this happens again!):
(I'm working in Enterprise 11.2 with no software updates currently happening and no other issues besides this that I'm aware of)
Short version:
I was suddenly getting an "out of memory" error in my browser when viewing a page in an Experience Builder app. This was happening in the builder and when viewing the published app, but not when viewing the draft app.
Long version:
I have a web app with LOTS of stuff in it, including >30 data sources and 11 pages all with various widgets. Despite this, the app's performance had been fine until today.
I've been working on one of the app's pages pretty steadily while not needing to touch any of the other pages for a while. As of yesterday at noon, I was able to edit this page and publish updates. When I started working on it again this morning, the browser would run out of memory when I tried to view this page in the builder or the published app. No other pages seemed to be affected, or at least, not so much that things weren't loading (the memory usage seemed high, but I didn't have numbers to compare it to). The draft app was totally fine. Other ExB apps I've built in the same portal didn't seem to be affected. I initially thought that something had gone wrong with the web map* that's used in this page, but all was fine. (*Said web map is composed of a bunch of different services--basically a general reference map--so lots of network activity when using it.)
What I tried:
- Restarted computer
- Shut down computer
- Tried Chrome instead of Edge
- Colleagues tried Chrome and Edge and confirmed draft app was fine
- Double-checked that the cache is being cleared every time I close Edge
- Searched this forum for similar instances (found dead threads, instances that don't apply (like using custom widgets), and performance tips I'm already taking advantage of (like using lazy loading for section views))
I went to have lunch, and now the builder, draft, and published versions are all working normally for the past ~90 minutes, and this persists after closing my browser, logging in again, etc.
My last resort before opening a support case with Esri was going to be duplicating the experience, since that would result in a draft that I could try republishing. (This app is so big though that I think it'd be a nightmare to duplicate.)
If anyone has literally any ideas about what might have happened or what else I could have tried, I'd love to hear it! I've had issues with ExB before, but nothing that wasn't eventually explainable or within my power to fix (if it happens again), and I'm hoping the latter is the case here.
