Closed Bug 1546381 Opened 6 years ago Closed 6 years ago

Upon launch, Firefox (66) creates multiple instances in background

Categories

(Firefox :: Untriaged, defect)

66 Branch
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: dreapadoir, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/73.0.3683.103 Safari/537.36

Steps to reproduce:

launch firefox 66

Actual results:

multiple instances (5) of firefox are launched (listed in Process Explorer)

Expected results:

Single instance of firefox. This had been the case until several days ago.
Recommended changes in about:config either did not prevent multiple instances, or prevent any tab opening.
Have switched to Google. Please advise if there has been a fix for this.

hello, firefox has been a multi-process application for a while already, so what you're describing already sounds like the expected & intended situation...
https://blog.mozilla.org/futurereleases/2016/08/02/whats-next-for-multi-process-firefox/
https://wiki.mozilla.org/Electrolysis

do you have any particular problem as a result of that?

Thanks for the response. Know about the multi-process and had edited the config previously. Forgot to re-edit it when reinstalling. (Problem which initiated the reinstall is apparently associated with UBlock add-on; after awhile FF hangs. Disabled UBlock, now using Ghostery which seems -so far- to prevent hanging.)

Hi dreapadoir,

Can you confirm if the issue you were having is now resolved by using Ghostery or if is still there please?

Thanks!

Flags: needinfo?(dreapadoir)

Luciana: The hanging problem seems to have been resolved by using Ghostery vs UBlock. UBlock was somewhat better at blocking, which might be why sites hung at loading.

Flags: needinfo?(dreapadoir)

Luciana: Regarding the multiple instances of FF, I successfully changed that in config (see note above to philipp.

Status: UNCONFIRMED → RESOLVED
Closed: 6 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.