Thousands of Errors in the Console

Map Editors Community WME Local Issues Bugs
1

Of late, I am seeing thousands of errors in the console in both production and beta WME. The screenshot below is from a fresh script-free beta WME load.

  • I opened an incognito windows and loaded WME beta. Even before logging in, the first 6 errors and the second violation appeared.
  • After logging in, the number of “[Report Only] This document requires ‘TrustedHTML’ assignment.” errors continued to climb to several hundred.
  • I panned the map a few times and the number of “[Report Only] This document requires ‘TrustedHTML’ assignment.” errors accellerated.
  • I zoomed the map twice. Upon zooming The remaining errors and violations appeared.

temp.jpg

1 Like
2

Hi Jason,

Could you please specify if you experience the issues besides displayed errors in console?

Also did you check with disabled scripts in you browser, correct? You mentioned that you used incognito mode, I wanted just double check the understanding.

Regards,
Nataliia

3

Yes. This is without scripts. I don’t notice any trouble using WME at first, but the longer the tab is open, the slower WME begins to respond.

4

Hi Jason,

Thank you for your reply. I have filed an internal issue for this, the team will review it. Also I want to tell that I will move this post to the WME Local Issues section as these issue seams to be country specific.

Regards,
Nataliia

1 Like
5

Hi Jason,

The team is investigating this case. They ask for your help: can you please check if disabling the Venues layer solves the WME errors?

Thank you in advance,
Nataliia

1 Like
6

Hi Nataliia,
Disabling the venues layer doesn’t solve it. I tested incognito without the venues layer and continued to see errors as I panned and zoomed the map.layers.jpg
errors.jpg

7

I’m also seeing this, and I’ve seen others reporting the same. This should be observable by anyone who looks at the browser console. I don’t think it’s a local issue.

Observed using incognito Chrome in ‘practice mode’ (not logged in) with all layers disabled. This is likely to be related to the Content-Security-Policy-Report-Only response headers that have been added to the editor page. [cf. trusted types]

1 Like
8

Same issue here. Just dragging the mouse around makes the warning counter go up. This is in incognito with no scripts / extensions running.Screen-Recording-2022-10-27-at-1.02.30-PM.gif

Edit-> Click on the image to watch the GIF

9

Hi Everyone,

Could you please check if this still happening?

Thank you in advance,
Nataliia

10

Yes, it is still happening. This screenshot is from 5 mins ago. Using Chrome 107.0.5304.87 on a Mac. No extensions or scripts.

These are the errors when I just start the editor. As I scroll the screen or select objects, the number of errors continue to grow.
Screen Shot 2022-11-03 at 06.24.19.png

11

It’s the same as before for me also, just moving the cursor around is still throwing errors. I am also running Chrome 107.0.5304.87 on a Mac.
Thanks.

12

Hi Abc1357,
Hi Ojlaw,

Thank you for your feedback, I will forward it to the team.

Best,
Nataliia

13

Same issue for me still. This screenshot was taken after having WME open for 20 seconds or so and zooming and panning.ss2.jpg

14

Hi Fuji2086,

Thank you for your report. I will update the internal ticket.

Regards,
Nataliia

15

Hi Everyone,

I want to ask you again to inform if the issue is still reproducible? We have enabled related fixes and the issue shouldn’t happen.

Regards,
Nataliia

16

Hi Nataliia, It looks like the issue isn’t resolved. I just tested Chrome incognito (no scripts nor extensions) Mac and this what I see in the console-Screenshot 2022-12-16 at 6.49.20 AM.png

1 Like
17

This continues to happen in both beta and production WME. This screenshot is from just now in beta WME and represents just a few seconds of WME usage incognito with no scripts. Logging in and panning/zooming to a point.ss1.jpg

18

I think I found some more information:

Here is a video I just created in Incognito WME Beta showing the errors.

NOTE: that the errors happen every time I move the mouse over the map. When I stop moving the mouse, the errors stop, when I start again, the errors start.

https://youtu.be/nTbNHrELjbw

1 Like
19

Hi Everyone,

The team identified that such errors appear due to the complexity of the deployment process. During previous back-end versions releases the database was under significant pressure. It led to a downtime and errors.

We’ve take various steps to reduce the likelihood of this happening again. Please keep an eye on the problem and leave comments in case you notice errors again.

Thank you in advance,
Nataliia

20

Hello Nataliia,
This is something we still continue to see in the current beta and production releases.temp.jpg