Este site está com funcionalidades limitadas enquanto realizamos manutenção para melhorar sua experiência de uso. Se nenhum artigo resolver seu problema e você quiser fazer uma pergunta, nossa comunidade de suporte pode te ajudar em @FirefoxSupport no Twitter e /r/firefox no Reddit.

Pesquisar no site de suporte

Evite golpes de suporte. Nunca pedimos que você ligue ou envie uma mensagem de texto para um número de telefone, ou compartilhe informações pessoais. Denuncie atividades suspeitas usando a opção “Denunciar abuso”.

Saiba mais

Esta discussão foi arquivada. Faça uma nova pergunta se precisa de ajuda.

Still problem with FF 57

  • 9 respostas
  • 2 têm este problema
  • 4 visualizações
  • Última resposta de MasterHarp

more options

Tried upgrading to latest version. Think 57.4 or 57.0.4. Same issues reported before. Reviewing Task Manager I see multiple FF processes. One of them consuming 95%+ of CPU. Response disappears. Unable for any other task to respond. Returned to using ESR. Still not clear what ESR is and its support lifetime. Reviews several post regarding changing various options. Not had much luck getting even the option screen to appear after CPU hogging starts.

Any ideas are appreciated.

Tried upgrading to latest version. Think 57.4 or 57.0.4. Same issues reported before. Reviewing Task Manager I see multiple FF processes. One of them consuming 95%+ of CPU. Response disappears. Unable for any other task to respond. Returned to using ESR. Still not clear what ESR is and its support lifetime. Reviews several post regarding changing various options. Not had much luck getting even the option screen to appear after CPU hogging starts. Any ideas are appreciated.

Todas as respostas (9)

more options

More than one process is normal for the current Firefox. http://www.ghacks.net/2016/07/22/multi-process-firefox/

Multi-process Firefox is codenamed "e10s". https://wiki.mozilla.org/Firefox/multiprocess


Try to disable multi-process tabs in Firefox. You can disable multi-process tabs in Firefox by setting the related prefs to false on the about:config page.

browser.tabs.remote.autostart = false browser.tabs.remote.autostart.2 = false

Type about:config<enter> in the address bar. If a warning screen comes up, press the I Accept the Risk button. At the top of the screen is a search bar.

more options

I have stayed current with FF releases. The machine in question worked just fine with FF 56 and previous. I will make the assumption that multi-process was default in that release. I have not changed any options manually before.

Still waiting on answer to my question about ESR.

more options

Means a bad FF install and did you remove all previous FF and FF folder before install FF57+? If not then you most likely have bad install leading to leakage RAM. I did that and have now such issue.

more options

masterharp said

Still not clear what ESR is and its support lifetime

Firefox; Extended Support Release {web link} ESR Notes System Requirements


https://support.mozilla.org/en-US/kb/switch-to-firefox-extended-support-release-esr Switch to Firefox Extended Support Release (ESR) for personal use

more options

To WestEnd: Sounds pretty drastic to me. What about my bookmarks and other personal items?

To Fred: Yes I already reviewed those items. As ESR works for me and NOT 57 I ask again what is the difference? A year from now when ESR "expires" then what? I am a personal user. I have been in the IT field for 25+ years.

Do I just keep trying 57 every now and again hoping it will work?

Alterado por MasterHarp em

more options

I called for someone to help with your questions.

more options

masterharp said

To Fred: Yes I already reviewed those items. As ESR works for me and NOT 57 I ask again what is the difference? A year from now when ESR "expires" then what? I am a personal user. I have been in the IT field for 25+ years.

The current Firefox 52 ESR will have a last update of 52.9.0esr on July 3rd. The next major version ESR will use is Firefox 60.0 to be out on May 8th.

If you had scrolled down on https://www.mozilla.org/firefox/organizations/ you would see this.

more options

Try to disable accessibility services in Firefox 57+.

You can try to modify multi-process settings to see if this has effect.

  • set number of content processes to 1 if it is currently set to a higher value (4)
    Options/Preferences -> General -> Performance
    remove checkmark: [ ] "Use recommended performance settings"
  • disable multi-process windows in Firefox

You can open the about:config page via the location/address bar. You can accept the warning and click "I accept the risk!" to continue.

more options

My frustration level is raising. Some posters have pointed me in positive directions. Over have not. I will start all over again.

I have been a long time user of FF. Kept current on updates. This came to a disastrous halt when 57 became available. In quick order machine became unusable. Downgraded to 56. FF worked again. I was informed this was the wrong solution. Directed to something called ESR. As I have stated multiple times I reviewed ALL the articles and ALL the items in the articles. I am a single personal user. As ESR worked and 57 did not I asked what I thought was a simple question. Why? To be more specific what is the difference between ESR and 57? Is ESR the "same or similar" code with option(s) disabled? My initial impression of the articles was ESR was a "temp fix" while the issue(s) with 57 were researched and addressed. I now am getting the impression that ESR and FF are similar but different tracks. As I have tried to ask before will I use ESR "forever" or will I be able at sometime to return to using "regular" FF? Yes I have seen updates that this forum is users not developers.

When I was full time working I would prefer to talk with the user regarding their problem/issue. Trying to use only written word create its own set of issues.