Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More
Open

Performance issues with Mac

I-Firefox App responsiveness
hmickelson
hmickelson

Hi there,

I am on a MacBook Air M3/8GB ram. I was really wanting to use Firefox due to your stance on privacy, etc. but here is my experience:

Yes, I keep a lot of tabs open - I do try to group them and hope that tabs in closed groups are deactivated, but I don't know this at all.

If I use Firefox all will seem well until my machine sleeps. On waking, it is excruciatingly slow - we are talking multiple seconds to even switch tabs or get the cursor to be "hot" when filling a form. Upon trying to quit (restarting being the usual first step), FF will ask confirmation and then close the windows, but will not completely quit, requiring me to force-quit. On restart it seems to behave again, at least for a while.

While I do see some evidence that others have this issue (memory leak?) there are no real methods or answers as to how, if at all, to fix this. It took a lot to get everything on FF working the way I like after leaving Chrome, but I really can't deal with this, and I think I will be looking at switching again - I guess to Safari.

I would love to know how to fix this, but really I don't imagine this is due to my system as much as the FF browser. That said, if you ahve any ideas, I would be open.

Hi there, I am on a MacBook Air M3/8GB ram. I was really wanting to use Firefox due to your stance on privacy, etc. but here is my experience: Yes, I keep a lot of tabs open - I do try to group them and hope that tabs in closed groups are deactivated, but I don't know this at all. If I use Firefox all will seem well until my machine sleeps. On waking, it is excruciatingly slow - we are talking multiple seconds to even switch tabs or get the cursor to be "hot" when filling a form. Upon trying to quit (restarting being the usual first step), FF will ask confirmation and then close the windows, but will not completely quit, requiring me to force-quit. On restart it seems to behave again, at least for a while. While I do see some evidence that others have this issue (memory leak?) there are no real methods or answers as to how, if at all, to fix this. It took a lot to get everything on FF working the way I like after leaving Chrome, but I really can't deal with this, and I think I will be looking at switching again - I guess to Safari. I would love to know how to fix this, but really I don't imagine this is due to my system as much as the FF browser. That said, if you ahve any ideas, I would be open.

You must log in to your account to reply to posts. Please start a new question, if you do not have an account yet.