Bl4Cc4t
GT2 started making Twitter slower for no clear reason.
Please check the following before you continue
- [ ] Bug happens with the newest version of GT2 (see the changelog)
- [ ] Checked FAQ
- [ ] Checked if the issue has not been reported before
Describe the bug From some point, logging into Twitter with GT2 started to be laggy than before. interacting with tweet has become way slower, and loading speed of timeline is sluggish for no clear reason. Even worse, when I try to write a tweet, the lag becomes worse and even closes/crashes the entire browser.
I tried deleting cookies, and it doesn't seem to affect much. Does anyone else have this issue?
Screenshots
Your configuration
- Browser : Brave Browser 1.31.88 Chromium: 95.0.4638.69
- Userscript Manager : Tampermonkey v4.13
just to be sure, does this also happen when you have script turned off?
possibly related: #258
just to be sure, does this also happen when you have script turned off?
possibly related: #258
Well, no. It's faster and functioning as usual when it's off.
Have you tried Firefox? I’ve seen other people report this on Twitter and it seems like it might be an issue with Chromium-based browsers.
I do not experience this myself, there is little I can about it I'm afraid. Maybe the script is too bloaty for your system, that could be some kind of explanation...
Weird. @Sandpie00, are there any errors in the console? Find it by pressing F12 and then going to the console tab.
Weird. @Sandpie00, are there any errors in the console? Find it by pressing F12 and then going to the console tab.
Yeah, a lot. I have my PC set to Italian, sorry about that
Caricamento non riuscito per lo <script> con sorgente “https://abs.twimg.com/responsive-web/client-web/polyfills.698d2a75.js”. [home:128:1](https://twitter.com/home) Bloccata richiesta multiorigine (cross-origin): il criterio di corrispondenza dell’origine non consente la lettura della risorsa remota da https://api.twitter.com/1.1/jot/client_event.json. Motivo: richiesta CORS non riuscita. Codice di stato: (null). [init] home [home:13:1037](https://twitter.com/home) Bloccata richiesta multiorigine (cross-origin): il criterio di corrispondenza dell’origine non consente la lettura della risorsa remota da https://api.twitter.com/1.1/jot/client_event.json. Motivo: richiesta CORS non riuscita. Codice di stato: (null). 41 [push] notifications [home:13:1037](https://twitter.com/home) Bloccata richiesta multiorigine (cross-origin): il criterio di corrispondenza dell’origine non consente la lettura della risorsa remota da https://api.twitter.com/1.1/jot/client_event.json. Motivo: richiesta CORS non riuscita. Codice di stato: (null). 2 [push] i/timeline [home:13:1037](https://twitter.com/home) Bloccata richiesta multiorigine (cross-origin): il criterio di corrispondenza dell’origine non consente la lettura della risorsa remota da https://api.twitter.com/1.1/jot/client_event.json. Motivo: richiesta CORS non riuscita. Codice di stato: (null). 2 [pop] notifications [home:13:1037](https://twitter.com/home) Bloccata richiesta multiorigine (cross-origin): il criterio di corrispondenza dell’origine non consente la lettura della risorsa remota da https://api.twitter.com/1.1/jot/client_event.json. Motivo: richiesta CORS non riuscita. Codice di stato: (null). 10 navbar toggled [home:13:1037](https://twitter.com/home) Bloccata richiesta multiorigine (cross-origin): il criterio di corrispondenza dell’origine non consente la lettura della risorsa remota da https://api.twitter.com/1.1/jot/client_event.json. Motivo: richiesta CORS non riuscita. Codice di stato: (null). [push] settings [home:13:1037](https://twitter.com/home) [replace] settings/account [home:13:1037](https://twitter.com/home) [push] settings/gt2 [home:13:1037](https://twitter.com/home) Bloccata richiesta multiorigine (cross-origin): il criterio di corrispondenza dell’origine non consente la lettura della risorsa remota da https://api.twitter.com/1.1/jot/client_event.json. Motivo: richiesta CORS non riuscita. Codice di stato: (null). [push] home [home:13:1037](https://twitter.com/home) Bloccata richiesta multiorigine (cross-origin): il criterio di corrispondenza dell’origine non consente la lettura della risorsa remota da https://api.twitter.com/1.1/jot/client_event.json. Motivo: richiesta CORS non riuscita. Codice di stato: (null). 6 Bloccata richiesta multiorigine (cross-origin): il criterio di corrispondenza dell’origine non consente la lettura della risorsa remota da https://api.twitter.com/1.1/jot/client_event.json. Motivo: richiesta CORS non riuscita. Codice di stato: (null).
I should add that what happens to OP with the pictures only happens if I have "Bigger image previews" enabled. But the site is just slower in general, especially when scrolling down, it takes a moment to load
@Sandpie00 argh. please make a screenshot of them the next time (why do I always forget to mention this). I can't see any errors by glancing over that wall of text, these should all be warnings (yellow) which can be ignored, if there are errors, they are red.
I'm sorry that you have a bad experience, but I can't think of a reason why this is happening... Since I have no problems on my end, it's impossible for me to fix this sadly.
Are there any other details about this issue? Does this slowdown happen all the time or after you have done certain things? Have you tried other browsers yet? Does logging out and logging back in do anything?
@Sandpie00 argh. please make a screenshot of them the next time (why do I always forget to mention this). I can't see any errors by glancing over that wall of text, these should all be warnings (yellow) which can be ignored, if there are errors, they are red.
I'm sorry that you have a bad experience, but I can't think of a reason why this is happening... Since I have no problems on my end, it's impossible for me to fix this sadly.
Are there any other details about this issue? Does this slowdown happen all the time or after you have done certain things? Have you tried other browsers yet? Does logging out and logging back in do anything?
They are all red. I've tried logging out and back in, nothing changed.