(In reply to lpy750 from comment #42) > As mentioned earlier, comment #30, hiding the throbber helps. I found that using userChrome.css to hide anything that animates: **.tab-throbber**, **#stop-reload-button**, **.tab-loading-burst[bursting]** (not a practical solution) restores about 99% of the speed. It's like there's another element somewhere that slows the browser down under some circumstances but I'm not sure what it is. This of course isn't a solution but I hope it can assist somewhat in tracking it down. Thanks for trying this, lpy750. The load delay is caused by suspending each channel from "http-on-modify-request" and "http-on-examine-response" by the extension. Why it's slowed down so much is still a question, but simply could be main thread flooding by too rapid vsync ticking. Keeping ni? on me.
Bug 1560090 Comment 44 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(In reply to lpy750 from comment #42) > As mentioned earlier, comment #30, hiding the throbber helps. I found that using userChrome.css to hide anything that animates: **.tab-throbber**, **#stop-reload-button**, **.tab-loading-burst[bursting]** (not a practical solution) restores about 99% of the speed. It's like there's another element somewhere that slows the browser down under some circumstances but I'm not sure what it is. This of course isn't a solution but I hope it can assist somewhat in tracking it down. Thanks for trying this, lpy750. The load delay is caused by suspending each channel from "http-on-modify-request" and "http-on-examine-response" by the extension. Why resuming is slowed down so much is still a question, but simply could be main thread flooding by too rapid vsync ticking. Keeping ni? on me.