Tridactyl causes each Firefox process to use an entire core and Firefox to become unresponsive.

notJerl commented 4 years ago

Brief description of the problem: I just updated to the newest version, and when enabled, Tridactyl causes Firefox each Firefox process to eat an entire core. When this happens, Firefox becomes pretty much unresponsive: new tabs won't load, existing tabs won't reload, other extensions stop functioning in tabs that are already open. Thankfully settings work so Tridactyl can be disabled, but essentially if I have the current version of Tridactyl enabled, Firefox becomes useless. And, with 6 Firefox processes eating 6 of my 8 cores, every other program experiences problems too. The problem persists until Tridactyl is disabled and Firefox is restarted; just disabling the add-on does not fix it.
Steps to reproduce: Start Firefox with the add-on enabled OR Enable the add-on while Firefox is running.
Tridactyl version (:version): 1.17.1
Firefox version (Top right menu > Help > About Firefox): 70.0.1 (64-bit)
Config (in a new tab, run :viewconfig, copy the url and paste it somewhere like gist.github.com): Can't do this, sorry.
Contents of ~/.tridactylrc or ~/.config/tridactyl/tridactylrc (if they exist): Doesn't exist.

notJerl commented 4 years ago

Disabling Tampermonkey as well allows the CPU usage to drop down after Tridactyl is disabled, but the problem is still present when Tridactyl is enabled regardless of whether Tampermonkey is enabled or not.

bovine3dom commented 4 years ago

Do you get the same issue with the beta?

glacambre commented 4 years ago

23:50:03 I updated Tridactyl, and now whenever Tridactyl is enabled, each Firefox thread takes up an entire core. 23:56:39 It looks like it's failing to set tridactyl.unfixedamo2. Might be causing a loop to not terminate or something. Lemme try setting it manually 23:59:11 Nope, no change. 00:01:51 It also locks up a lot of Firefox' functions when it's happening. Tabs will not load. just period. 00:02:10 It doesn't get fixed until I not only disable Tridactyl, but completely restart Firefox. 05:08:36 Managed to grab an old version from my laptop for now. Vimium and Vim Vixen just didn't cut it for replacements.

How did you come to the conclusion that the issue came from unfixedamo2?

notJerl commented 4 years ago

Sorry for the delay responding, I've been a little busy.

No, it doesn't happen on the latest beta build from 2019-11-17.

I didn't really come to the conclusion that the issue came from unfixedamo2 for any particular reason... I just thought about what was obviously different between the two versions that I could check, and thought "huh, I wonder if it got stuck in some sort of loop trying to unfix AMO because Tridactyl's never actually been able to write a tridactylrc for me before", so I decided to check if that seemed to be the case.

protrolium commented 4 years ago

I seem to be stuck in a similar loop. I just updated to latest Firefox (71.0) and Tridactyl/Firefox seems to be stuck in a loop. I only get white pages, none of the history or new tabs display, and all Tridactyl keybindings and commands are not passed. Because I disabled the GUI via :guiset I cannot do anything with Firefox.

Is there anything beyond Refreshing Firefox that I can try to address this?

glacambre commented 4 years ago

@protrolium Try removing CSS rules in ~/.mozilla/firefox/profile/chrome/userChrome.css one by one and restarting firefox each time.

notJerl commented 4 years ago

Firefox somehow ate my profile. After reinstalling everything on a fresh profile, this issue is no longer occurring.

tridactyl / tridactyl

Tridactyl causes each Firefox process to use an entire core and Firefox to become unresponsive. #1997