Experience Builder measuring tool performance

[Maryse]

Some users have reported issues with the Experience Builder measuring tool since the recent update - both the default measuring tool, accessible from the map settings and the measuring tool widget.

It's quite slow to use, freeze often and randomly crash the whole Experience Builder (it was working fine before that).

Is it a known issue ?

[JakeEdington]

This has been a significant issue for me as well. My webmap essentially becomes unusable after using the measuring tool. The only way to solve this has been to refresh the page. 

[Wei_Ying]

Thanks all of you! We will try to figure out from our side. But if any of you can share an repro app to us that would be really helpful to us! Appreciated. 

[emwing]

https://experience.arcgis.com/experience/b1d61276fee846cea8f980a0c41cea28 This is to the City of Boise public map viewer; you are welcome to test. We did note that the AGOL update in mid-November made the issue a little less problematic. Our users had to work harder to get Experience Builder to crash. It was enough of an improvement to resolve our major concerns. We just try to remind our users that if you turn on twenty layers at once that performance may be a problem. It's been a slow transition to get users away from one web app that has every layer they could ever possibly want.

[ericsamson_tract]

Hi all,

I have been working on this issue with ESRI. The problem stems from the javascript SDK measurement tool, so it may be a while until there is a solution.

In the meantime, I created a custom measurement widget that should not slow down an experience builder application. It is very bare bones, so please feel free to improve upon if needed. Attached here.

[jharringtondnr]

We're experiencing the same issue in our Online EB app. Assuming you're using EB in Enterprise Portal so this app won't work for us as we haven't developed the capability to use third party EB apps in ArcGIS Online yet. 

[ericsamson_tract]

They are working on a fix for this internally. They weren't really able to duplicate the issue, (even though I have documented on this thread how to duplicate it in detail, using the public Boise web experience app someone shared). I am not fully convinced they are taking the issue seriously, so I wouldn't expect a quick turn around. It also appears that the solution may have to come from the JavaScript SDK team, not experience builder. I've since updated my widget a bit, so I am attaching it here again for anyone else that finds this thread.

[jharringtondnr]

Funny timing. I just closed my case with support and they were able to duplicate the issue. They couldn't duplicate it as they were only running the tool with a few layers in either Map Viewer or Experience Builder. Once they received all the layers I was using in my map, they were able to replicate the issue and it is now logged as a bug! Not sure if the bug number is specific to my case or if you can view it, but below is the bug number. 

BUG-000174087

[ericsamson_tract]

Awesome, good news!