WMF devs are reluctant to add a simple preference to disable this often useless extension (see bug 46306).

I'm excited how the will react to this request now that it's obvious this extensions is even causing severe problems.

Probably with a WONTFIX, eh.

(In reply to comment #0)

The amount of complaints about freezing browsers has been substantial since
the deploy of ULS to English Wikipedia.

Do you refer to https://en.wikipedia.org/wiki/Wikipedia:Village_pump_%28technical%29#Unresponsive_script or is there more feedback in other places that you refer to?

https://en.wikipedia.org/wiki/Wikipedia:Village_pump_(technical)#Heavy_Javascript_load_after_loading_some_articles.

And several Helpdesk reports, as well as multiple people complaining about VE, while probably the ULS is causing the slowness.

Also, it's currently deployed globally, not just on en.wp.

Also reported at pl.wp: https://pl.wikipedia.org/wiki/Wikipedia:Kawiarenka/Kwestie_techniczne#Ostrze.C5.BCenie:_Skrypt_nie_odpowiada

Just a note that the Language Engineering team responsible for ULS will be holding an office hour later today, at 17:00 UTC on
#wikimedia-office (on Freenode): http://www.mail-archive.com/wikitech-l@lists.wikimedia.org/msg69718.html

I have deployed a performance fix for ULS webfonts tonight.

Currently I see no pressing need or consensus to disable ULS completely and I would much prefer us to work on incremental improvements.

(In reply to comment #8)

I have deployed a performance fix for ULS webfonts tonight.

Currently I see no pressing need or consensus to disable ULS completely and I
would much prefer us to work on incremental improvements.

Original reporter of the problem on en.wiki declares the problem fixed after today's deploy, which – Niklas says – made things 4 times faster.
https://en.wikipedia.org/w/index.php?title=Wikipedia%3AVillage_pump_%28technical%29&diff=563728176&oldid=563727357

Closing this one as a duplicate (it wasn't properly a WORKSFORME but the original request wasn't FIXED either) of bug 50836 as suggested for bug 51073 comment 9.

• This bug has been marked as a duplicate of bug 50836 ***