4 ms·
After nearly a decade of using Chrome I decided to give FF another shot, having initially switched over due to slowness, an insatiable thirst for memory, and th
by EpicEng 9y ago
After nearly a decade of using Chrome I decided to give FF another shot, having initially switched over due to slowness, an insatiable thirst for memory, and the single process model. I installed on both Windows (10 Pro) and Mac OS.
Initial impressions were good; it seemed snappy, I liked the UI, and it was using less memory than Chrome with the same number of tabs open. A couple of days in things went downhill.
On Mac OS I was getting short freezes every ~10 seconds. I found similar complaints ranging over a period of nearly five years, but no clear resolution. This morning I had FF lock up multiple times while editing Jira tickets. Since FF is still a single process, the entire browser was locked up and required a hard kill, which cost me work.
So, no thanks mozilla, back to Chrome. I know this is one person with one experience, but man, this one experience was pretty off-putting. Maybe I'll try again in another decade.
- nod 9y agoThis is not relevant to the subject of the article.
- EpicEng 9y agoYeah you're right, I suppose I saw an opportunity to rant on a recent experience
- Max_Mustermann 9y agoYou probably used version 55. If you're willing to give it another try, it might work quite differently once is on version 57, Nov 14, from what I last read: massive changes are coming, but mainly starting from that version.
- EpicEng 9y agoI did, I'll give it a try
- veeti 9y ago> Since FF is still a single process Multiprocess has been gradually rolled out since last year. Check about:support, you might have some ancient addon installed that isn't compatible.
- nindalf 9y agoI'd encourage you to give Firefox another shot. They've improved a lot in the last couple of versions. More pertinent, in my opinion, is that they're on a promising trajectory and I'd expect it to be incredible in the medium term.
- EpicEng 9y agoMy hand up is that this _was_ me giving FF another shot... and it failed miserably. Not sure how many more shots I have in me.
- 482794793792894 9y agoFirefox is not anymore singleprocess. It will fall back to singleprocess, if you have an extension installed that's not yet compatible with multiprocess. With the aforementioned Firefox 57, they will switch over to a new extension API and this will also result in those old singleprocess extensions being thrown out, so that's why they haven't bothered trying to make this transparent to users. Also, they are switching out the UI with Firefox 57, so I hope you like this one, too: http://design.firefox.com/people/shorlander/ http://design.firefox.com/people/shorlander/