Sykje yn Support

Mij stipescams. Wy sille jo nea freegje in telefoannûmer te beljen, der in sms nei ta te stjoeren of persoanlike gegevens te dielen. Meld fertochte aktiviteit mei de opsje ‘Misbrûk melde’.

Mear ynfo

Dizze konversaasje is argivearre. Stel in nije fraach as jo help nedich hawwe.

Firefox won't show any pages, or options. have to about:support refresh every time

  • 4 antwurd
  • 8 hawwe dit probleem
  • 5 werjeftes
  • Lêste antwurd fan jhenneike

more options

After update to Firefox 50, I cannot access any sites or open Firefox->options when starting firefox. Have to perform a 'refresh' by going to 'about:support' and clicking refresh. Then it works, but only for that session.

After update to Firefox 50, I cannot access any sites or open Firefox->options when starting firefox. Have to perform a 'refresh' by going to 'about:support' and clicking refresh. Then it works, but only for that session.

Keazen oplossing

hi jhenneike, can you please try the following and see if that works: enter about:config into the firefox address bar (confirm the info message in case it shows up) & search for the preference named browser.tabs.remote.autostart.2. double-click it and change its value to false.

Dit antwurd yn kontekst lêze 👍 1

Alle antwurden (4)

more options

Keazen oplossing

hi jhenneike, can you please try the following and see if that works: enter about:config into the firefox address bar (confirm the info message in case it shows up) & search for the preference named browser.tabs.remote.autostart.2. double-click it and change its value to false.

more options

Thank you philipp. My firefox now loads normally again. Is this a new default setting? or what could have triggered this? I ask because I have several users at my company that have this same behavior, but no everyone is affected...

more options

this is the setting that controls the new multiprocess-architecture in firefox ("e10s"): https://blog.mozilla.org/futurereleases/2016/08/02/whats-next-for-multi-process-firefox/ in firefox 50, e10s was enabled for more users on firefox release (everyone with compatible addons), so that's probably the reason why you started seeing it after the last update...

could you point your it department to chime in at bug https://bugzilla.mozilla.org/show_bug.cgi?id=1319055 which was filed just today as well...

more options

I will pass the request on to our IT folks.

Thanks again.