ძიება მხარდაჭერაში

ნუ გაებმებით თაღლითების მახეში მხარდაჭერის საიტზე. აქ არასდროს მოგთხოვენ სატელეფონო ნომერზე დარეკვას, შეტყობინების გამოგზავნას ან პირადი მონაცემების გაზიარებას. გთხოვთ, გვაცნობოთ რამე საეჭვოს შემჩნევისას „დარღვევაზე მოხსენების“ მეშვეობით.

ვრცლად

64 Bit FF 56.0 terrible memory hog, sluggish.

  • 28 პასუხი
  • 16 მომხმარებელი წააწყდა მსგავს სიძნელეს
  • 1 ნახვა
  • ბოლოს გამოეხმაურა RedLewis

Have been using FF for 10 years. Current machine is an I7, 8 CPU, 12 Gig.

Approx 5 days ago upgraded to FF 56.0 64 bit via auto update.

FF immediately became sluggish using 15 - 20 % CPU but worse offender is it being a memory hog. Running my standard desktop arrangement of two browser sessions each with 3 - 5 tabs and a email client..

Memory usage before FF 56.0 was 4-5 Gigs. FF 56.0 immediately moved this to 5 Gigs at startup and within 2-3 hours memory usage moves to 8-10 gigs. I have spent the last 4 days restarting FF 56.0 several times a day but the same pattern continues to repeat itself.

Finally this morning moved back to FF 64 bit 55.0.3 and everything is fine again.

The FF 56.0 is the same in safe mode, new profile, whatever, it doesn't matter. It is broke!

Have been using FF for 10 years. Current machine is an I7, 8 CPU, 12 Gig. Approx 5 days ago upgraded to FF 56.0 64 bit via auto update. FF immediately became sluggish using 15 - 20 % CPU but worse offender is it being a memory hog. Running my standard desktop arrangement of two browser sessions each with 3 - 5 tabs and a email client.. Memory usage before FF 56.0 was 4-5 Gigs. FF 56.0 immediately moved this to 5 Gigs at startup and within 2-3 hours memory usage moves to 8-10 gigs. I have spent the last 4 days restarting FF 56.0 several times a day but the same pattern continues to repeat itself. Finally this morning moved back to FF 64 bit 55.0.3 and everything is fine again. The FF 56.0 is the same in safe mode, new profile, whatever, it doesn't matter. It is broke!

ყველა პასუხი (8)

Well no-one ever solved the 56.N issue but they released 57.N

57.N is for me more responsive than 56 but is really a memory hog.

With two browser windows open with 3 tabs in each FF 57 now runs 7 separate processes.

Memory usage starts about 2 gigs and in 3 days is at 6+ gigs.

57 made obsolete 5 of my most used add-ons. Sigh...

Maybe 58?

RedLewis said

I am having the same problem as BillMason. It started for me about a week ago when auto update went to quantum 57.0 64-bit version. It is not just sluggish, it is unusably slow. I am having to use IE to type this. System: i7 CPU 2.80 GHz, 12.0 GB ram, 64-bit OS and processor, Win 10 Pro, ver 1709 OS build 16299.64 Uses 22% CPU and 1.7+ GB memory.

Please see the reply from philipp in this thread regarding accessibility services in case this bug is affecting your system: Firefox 57 hangs up.

Am I correct that if I use 55 or something old that I would not get security fixes?

That is correct. The update for Firefox 55 was Firefox 56, etc.

BillMason said

57.N is for me more responsive than 56 but is really a memory hog. With two browser windows open with 3 tabs in each FF 57 now runs 7 separate processes.

You can adjust the number of content processes, but I don't know if that will make a lot of difference. See: Firefox's performance settings.

57 made obsolete 5 of my most used add-ons.

This thread is a little long already. Do you want to start a new question about the ones you need replaced?

"You can adjust the number of content processes, but I don't know if that will make a lot of difference. See: Firefox's performance settings."

It is set at the default of 4. However that appears to "4" per browser session, not 4 total.

So it appears that it attempts to open 4 processes per browser session or in my case it opened 7 with two browser sessions. I guess that is because I only have 8 "CPU's" available. (Why not 8?)

Not that I normally would, but I did open a third browser session out of curiosity and the number of processes stays at 7.

But anyhow, the Performance Setting only applies per browser session, not total FF usage.

Again after restarting the two browser sessions memory use starts at 3 gigs.

I will open a different thread on the disabled add-ons.

ALL other people answering and posting do not do so.

You confuse the issues and your answers do not apply.

Become a Contributor if wanting to solve issues.

Pkshadow said

ALL other people answering and posting do not do so. You confuse the issues and your answers do not apply. Become a Contributor if wanting to solve issues.

I am having trouble relating this comment to the conversation, can you clarify?

This must be a rare problem to go so long unresolved. Can those with it see a common environment that might narrow it down? Mine is:

57.0 (64-bit) System: i7 CPU 2.80 GHz, 12.0 GB ram, 64-bit OS and processor, Win 10 Pro, ver 1709 OS builds 16299.64, 16299.98, Norton Security

thanks very much, Red

Hi RedLewis, it's would be better to try a Firefox 57 thread.

Does anything in this article help: Quick fixes if your Firefox slows down?

Some Windows 10 users are encountering severe performance problems with Firefox 57 related to accessibility services. Please see the reply from philipp in the following thread in case this bug is affecting your system: Firefox 57 hangs up.

jscher2000 said

Hi RedLewis, it's would be better to try a Firefox 57 thread. Does anything in this article help: Quick fixes if your Firefox slows down? Some Windows 10 users are encountering severe performance problems with Firefox 57 related to accessibility services. Please see the reply from philipp in the following thread in case this bug is affecting your system: Firefox 57 hangs up.

jscher2000,

Thank you!, your link was very helpful. Sorry, I did not realize there was another thread.

I think I fixed the problem by following the simple one-slick solution:

"go to the firefox menu ≡ > options > privacy & security panel and under permissions check the setting to prevent accessibility services from accessing your browser. "

Nice not to have to use IE anymore...

Red

  1. 1
  2. 2