Why ExB so memory hungry?

JoabelBarbieri — Fri, 07 Aug 2026 13:46:40 GMT

Hello Esri Community and Experience Builder developers,

I am troubleshooting a performance issue with an ArcGIS Experience Builder application and would appreciate feedback from the community and Esri development team.

The application is causing very high resource usage in the browser:

Memory usage: ~1.75 GB RAM
CPU usage: ~140%+ (multiple cores)
Browser: Chrome/Edge
Impact: Laptop fan runs continuously, system becomes sluggish
The issue occurs while running the Experience Builder application (not just during initial loading). The browser process remains under heavy CPU load.

I am trying to determine whether this is caused by:

A specific widget behavior
Map rendering/WebGL issues
Feature layer complexity
Excessive queries or refresh cycles
A known Experience Builder performance issue
Things I would like advice on:

Are there recommended tools or methods to identify which Experience Builder widget or map layer is consuming CPU?
Are there known performance issues with certain widgets (Map, List, Table, Filter, Chart, etc.)?
Are there best practices for diagnosing high CPU usage in Experience Builder apps?
Are there browser developer tools, ArcGIS logs, or debugging methods that can help isolate the cause?
Current observations:

Chrome Task Manager shows the Experience Builder tab consuming ~1.75 GB memory.
CPU usage frequently exceeds 100%.
The behavior appears related to the running application rather than the initial loading process.
I have already done:

Reducing visible layers
Simplifying symbology
Limiting labels
Optimizing feature services
Testing published vs. builder mode
However, I would like to identify the actual source of the CPU usage rather than blindly removing functionality.

If anyone from the Experience Builder team or experienced developers has suggestions for profiling or debugging this type of issue, I would greatly appreciate your guidance.

Thank you!

Re: Why ExB so memory hungry?

JudithWammack — Fri, 07 Aug 2026 14:00:11 GMT

@JoabelBarbieri , I have a quick question. Is the map where you're experiencing this issue publicly accessible? I used to encounter similar problems, but after making several browser-related changes, the issues were resolved.

I'm wondering if those same changes might help in your situation. If the map is available, I'd be happy to test it.

For context, one of my department's maps contains approximately 98 layers within a single image layer. We experienced performance issues early on, but I was able to resolve them through research and browser configuration changes, without assistance from ESRI.

topic Re: Why ExB so memory hungry? in ArcGIS Experience Builder Questions

Why ExB so memory hungry?

Re: Why ExB so memory hungry?

Re: Why ExB so memory hungry?