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 ?
I have a prototype available for the moment here: https://experience.arcgis.com/experience/b1d61276fee846cea8f980a0c41cea28 This application is still in development; there may be a few dead layers. This application has few enough hosted feature layers that it doesn't cause a browser crash when the measure tool is used for most users. For our other more complex maps with 80-100 layers, we found changing to an imagery service was less RAM intensive for our users. We are well aware that 100 layers for one map is not best practice and to expect performance issues. It's been a trade off: either configure a few high resources applications or force some user groups to juggle between multiple applications. Our users were more receptive to a few applications with slightly worse performance.
Hi @emwing ,
Really appreciate for sharing the application. But as I tried, it looks good no obvious performance issue is found. Do you mind sharing a screenshot video or GIF demonstrating what you are seeing? Appreciated!
@Wei_Ying I just tested the measure tool on @emwing 's application and experienced the same slow down that we are seeing. If you want to see what we are talking about:
1. Open:
2. IMPORTANT: To get a sense of the speed that the app usually behaves, pan and zoom around the map for a little before making a measurement.
3. Create a line measurement
4. Before clearing the line measurement, create an area measurement (the slow down for me happens either way, but having two measurements drawn does seem to make it more pronounced)
5. Now try panning and zooming around the map, you will notice that the app has substantially slowed down. Compared to how panning was before using the measure tool, it makes the app unusable. Our users have reported the app crashing completely.
The problem does not resolve if you clear the measurement graphics. Holding control does not avoid the slow down. It only resolves if you refresh the web page.
Also, this problem gets even worse the more measurements you make. It seems to be linear, the more measurements you make, the slower the panning becomes, until you basically can barely move the map around
Just want to confirm are you seeing the performance issue in the Measurement widget loading or when during measuring?
@Wei_Ying The performance issue is when measuring distance and area.
I haven't had time to re-create a WebApp for public sharing, but the issue seems to resolve, when drastically reducing the number of layers available (as mentioned by @emwing).
@Maryse Thanks for the update! I have tried the same scenario again by adding many layers but I didn't see significant performance issue.
Would you do me a favor to try two things:
1. For the previous map with which you seeing measuring performance issue in ExB, could you try open it in Map viewer and use the Measurement tools there see is same performance problem occurs?
2. While you are seeing the issue, you you try measuring while holding "CTRL" key? With that how the performance looks (Because snapping is enabled by default for measuring, holding the CRTL key can temporarily disable it. We are guessing the snapping with many layers may have problem.)
Thanks,
Wei
@Wei_Ying Thank you, please see my answers below:
1. The performance issue is the same in Map Viewer
2. Holding CTRL helps with "plotting" points to measures a distance or an area, but the overall issue is the same : the widget is slow and potentially crash from the moment it's open
(e.g. Just now, I measured a distance holding CTRL, then tried to measure an area, which crashed the whole ExB)
Thanks
I am experiencing this as well. As soon as any of the users use the measurement tool, the app slows down exceptionally. Users have to refresh after using to be able to use the app. One user had the app crash completely.
@Wei_Ying My map has about 50 layers on it, so it's pretty memory intensive. I can't share my app easily, but happy to hop on a call to show you what we are seeing.