This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Caută ajutor

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.

Află mai multe

Acest fir de discuție a fost arhivat. Adresează o întrebare nouă dacă ai nevoie de ajutor.

What is the new PID structure in the new Firefox?

  • 6 răspunsuri
  • 1 are această problemă
  • 9 vizualizări
  • Ultimul răspuns de TyDraniu

more options

The older Firefox ran under one PID; the newer FF runs with one main PID and six subsidiary PIDs, per ProcessExplorer. I have a situation where the primary PID and one of the auxiliary PIDs uses 50-70% CPU for brief periods of time. I am trying to determine what is causing FF to use the CPU. I ran a two-minute Process Monitor trace on the main PID (8792) and one auxiliary PID (14268):

https://www.dropbox.com/s/ibrkyqggdr8oodn/Firefox.180617.1142.pid8792.CSV?dl=0 555k https://www.dropbox.com/s/9cfdpjw76u4irpj/Firefox.180617.1142.pid14268.CSV?dl=0 24k

are the links to the two ProcessMonitor .csv files, as I cannot upload non-image files to this thread. Can someone tell me what each of these PIDs is doing to cause large spikes in CPU \usage? Thanks.

The older Firefox ran under one PID; the newer FF runs with one main PID and six subsidiary PIDs, per ProcessExplorer. I have a situation where the primary PID and one of the auxiliary PIDs uses 50-70% CPU for brief periods of time. I am trying to determine what is causing FF to use the CPU. I ran a two-minute Process Monitor trace on the main PID (8792) and one auxiliary PID (14268): https://www.dropbox.com/s/ibrkyqggdr8oodn/Firefox.180617.1142.pid8792.CSV?dl=0 555k https://www.dropbox.com/s/9cfdpjw76u4irpj/Firefox.180617.1142.pid14268.CSV?dl=0 24k are the links to the two ProcessMonitor .csv files, as I cannot upload non-image files to this thread. Can someone tell me what each of these PIDs is doing to cause large spikes in CPU \usage? Thanks.

Toate răspunsurile (6)

more options

You will likely find a lot of information about this topic from the Multiprocess Firefox documentation on MDN.

more options

You may see three or more Firefox processes running.

  • one process for the main Firefox thread (user interface)
  • one or more content processes set via dom.ipc.processCount
    Options/Preferences -> General -> Performance
    remove checkmark: [ ] "Use recommended performance settings"
  • one process for the compositor thread (Windows;graphics)

You can find the current multi-process state on the Troubleshooting Information (about:support) page.

  • "Help -> Troubleshooting Information" -> "Application Basics":
    Multiprocess Windows
    Web Content Processes
more options

Thanks for the info on the new PID structure. Is there anyone who can look at the two ProcessMonitor CSV files to try to determine what was causing the CPU spikes in the two-minutes I ran the ProcessMonitor trace? Thanks.

more options

HI, unfortunately that format can not be uploaded. I would not know what caused the spikes, with out info on your Extensions that are running as it is possible it was one of those if it was a security one.

Do make sure that there is a Check Mark here : To be Checked and turned off unless needed for accessibility : Please : go to the Firefox 3 Bar Menu --> Options --> Privacy & Security panel and under Permissions check (put a tick in the box) the setting to Prevent Accessibility Services from accessing your browser.

more options

I am not sure what you mean by "that format can not be uploaded. " The two files are .csv files, and I was able to add them to this thread. I have posted similar ProcessMonitor .csv files on this forum, and others have been able to process them.

As for add-ons - I ALWAYS run in safe-mode,

more options

If you want to report a performance issue:

1. Read this instruction: https://developer.mozilla.org/en-US/docs/Mozilla/Performance/Reporting_a_Performance_Problem 2. Capture a perf profile. 3. Create a bug on https://bugzilla.mozilla.org/enter_bug.cgi (simply describing, what's going on). 4. Attach captured profile to that bug. 5. You can paste a link to your bug here to help us follow it.