>>106327952
you should enable them again
then go to about:processes then run a profile on them as you navigate around for a bit. you'll be able analyze details and see which extension exactly is the hog.