News for hackers. Stuff that matters.

A comment on Firefox 61.0 Released. Parent comment

Re:Firefox 61.0 Released by greglindahl on Tuesday June 26, 2018 @12:38PM (#17402049)
Firefox has tools to figure out which tabs are causing problems, try about:performance. Any freeze of minutes is generally caused by a memory leak in the javascript of a particular page.
[ Parent | on HN ]
Re:Firefox 61.0 Released by kemayo on Tuesday June 26, 2018 @01:54PM (#17402679)
I thought the recent work on multi-process stuff would have gotten rid of that? The browser chrome not being affected by in-page issues seems like a fairly important goal there...
[ Parent | on HN ]
Re:Firefox 61.0 Released by shock on Tuesday June 26, 2018 @05:39PM (#17404196)
I did look in about:performance, nothing obvious was there. I think it's rather because I have many tabs, not because of a specific tab.
[ Parent | on HN ]
Re:Firefox 61.0 Released by computerfriend on Tuesday June 26, 2018 @09:23PM (#17405164)
I have about 200 tabs on my work machine and something even worse on my personal one and have never seen this, so unless you're a serious tab hoarder I doubt it's that.
[ Parent | on HN ]
Re:Firefox 61.0 Released by pbhjpbhj on Tuesday June 26, 2018 @04:01PM (#17403572)
>about:performance //

Where's that in the menus?

[ Parent | on HN ]
Re:Firefox 61.0 Released by untog on Tuesday June 26, 2018 @04:23PM (#17403702)
It's a URL
[ Parent | on HN ]