Hilfe durchsuchen

Vorsicht vor Support-Betrug: Wir fordern Sie niemals auf, eine Nummer anzurufen, sie per SMS zu kontaktieren oder persönliche Daten preiszugeben. Bitte melden Sie verdächtige Aktivitäten über die Funktion „Missbrauch melden“.

Learn More

Which process should I end to kill Firefox 57.0?

  • 3 Antworten
  • 7 haben dieses Problem
  • 2039 Aufrufe
  • Letzte Antwort von jscher2000

more options

Occasionally, any piece of complex software will stop responding, and need to be forcibly shut down. I had such an event today when the right-click (context) menus and title-bar menus wouldn't appear. However, since upgrading to FF 57, I now see about 6 Firefox tasks and 6 firefox.exe processes in the Task Manager (Windows 10).

I like the feature of being able to restart Firefox (after killing it) and have my previous session restored, but the processes aren't really distinguishable in Task Manager, so I don't know which one to end/kill. I had to kill a few of them today before I stumbled upon the "main" process and Firefox disappeared. Can you help me to identify the main process for next time?

Ausgewählte Lösung

I found that by sorting the tasks in task manager by name (instead of by memory or CPU usage, for instance), the task manager groups them into Apps and Background Processes. Then it's easy to see which one is the root task.

Diese Antwort im Kontext lesen 👍 1

Alle Antworten (3)

more options

How to crash Firefox (All Systems); Instructions here; https://developer.mozilla.org/en-US/docs/Mozilla/How_to_report_a_hung_Firefox

This link has a program that can crash Firefox.


How long is Firefox running before there is a problem?

Start Firefox in Safe Mode {web link} by holding down the <Shift> (Mac=Options) key, and then starting Firefox.

A small dialog should appear. Click Start In Safe Mode (not Refresh). Is the problem still there?

https://support.mozilla.org/kb/Firefox+is+already+running+but+is+not+responding

https://support.mozilla.org/en-US/kb/firefox-slow-how-make-it-faster

https://support.mozilla.org/en-US/kb/firefox-uses-too-many-cpu-resources-how-fix

https://support.mozilla.org/en-US/kb/firefox-uses-too-much-memory-ram

https://support.mozilla.org/en-US/kb/firefox-hangs-or-not-responding

more options

Ausgewählte Lösung

I found that by sorting the tasks in task manager by name (instead of by memory or CPU usage, for instance), the task manager groups them into Apps and Background Processes. Then it's easy to see which one is the root task.

more options

That's clever.

If you are using the Details tab and you add the Command Line column, that also will help you distinguish the content processes from the main process.