4 ms·
Meanwhile, I sit here with the firefox usage pegged at 50%, and no way to tell which tab is killing the CPU. There's a 9-year-old bug open, requesting this feat
by discardorama 11y ago
Meanwhile, I sit here with the firefox usage pegged at 50%, and no way to tell which tab is killing the CPU. There's a 9-year-old bug open, requesting this feature. Now, before the fanboys jump in and say "it's open source, why don't you do it?", I'll admit that my hacking skillz are not enough to dive into Firefox source.
- GigabyteCoin 11y ago>There's a 9-year-old bug open, requesting this feature. Well is it a feature-request that a simple firefox extension could handle? Or is it a bug report about something inherently wrong with Firefox? Because it sounds like a feature request to me.
- discardorama 11y agoIt's a feature request. Without access to the innards, I don't think an extension would be able to do it.
- kevingadd 11y agoThere's been a CPU profiler in the debugging tools for over a year, and before that there was one in the addon repository with documentation on the mozilla wiki. Could be easier (like Chrome's task manager) but it's not as hard as you seem to think it is. P.S. Chrome's task manager isn't accurate anymore because now a bunch of work is offloaded from the per-page processes to special catch-all processes like the 'GPU Process'. So this is actually a harder problem to solve than it seems at first glance...
- dblohm7 11y agoThere is also about:performance, though I'm not sure whether that has made its way to release yet.
- ucho 11y agoI guess they were waiting for Electrolysis to be integrated in official release, has that already happened?