Problem Posting With Firefox

By +Gary7
in Site & Forum Issues

 Share

Recommended Posts

Grand Master

+Gary7 Subscriber²

Posted
  • Author
  • Subscriber²
Posted
  On 12/10/2016 at 15:15, Zlip792 said:

Firefox version? Addons Installed? OS version?

 

Tried to clear cache and cookies? Ctrl + F5?

Expand  

I did all of that. standard add-ons no flash no e10s Firefox 49.0.1 64 bit. Addons adblock, Tab Mix, Colt they are all signed.

Grand Master

+Zlip792 MVC

Posted
  • MVC
Posted
  On 12/10/2016 at 15:23, Gary7 said:

I did all of that. standard add-ons no flash no e10s Firefox 49.0.1 64 bit. Addons adblock, Tab Mix, Colt they are all signed.

Expand  

Tried turning back on - e10s. It will make only particular tab to crash rather than whole browser.

 

Also FX is moving with e10s on, so you should expect more issues, if it is turned off.

Grand Master

+Gary7 Subscriber²

Posted
  • Author
  • Subscriber²
Posted
  On 12/10/2016 at 15:28, Zlip792 said:

Tried turning back on - e10s. It will make only particular tab to crash rather than whole browser.

 

Also FX is moving with e10s on, so you should expect more issues, if it is turned off.

Expand  

How do I turn it on? I never turned it off, I just installed Fx 40 64 Bit the way it was..

Grand Master

+Zlip792 MVC

Posted
  • MVC
Posted
  On 12/10/2016 at 15:53, Gary7 said:

How do I turn it on? I never turned it off, I just installed Fx 40 64 Bit the way it was..

Expand  

Go to 'about:support' and confirm whether it is turned on or off:

 

e10s.PNG

 

Now go to 'about:preferences#general' and tick the 'Enable multi-process Firefox'.

Grand Master

+Gary7 Subscriber²

Posted
  • Author
  • Subscriber²
Posted
  On 12/10/2016 at 16:02, Zlip792 said:

Go to 'about:support' and confirm whether it is turned on or off:

 

e10s.PNG

 

Now go to 'about:preferences#general' and tick the 'Enable multi-process Firefox'.

Expand  

In about:support it says it is disabled by adons. Which one would do that? I Toggled it to true in about:config.

Grand Master

+Zlip792 MVC

Posted
  • MVC
Posted
  On 12/10/2016 at 16:12, Gary7 said:

In about:support it says it is disabled by adons. Which one would do that? I Toggled it to true in about:config.

Expand  

Some accessibility addon might be causing the issue. Since accessibility causes issues with the electrolysis currently.

 

Can you post screenshot from about:support for the Extensions section?

Grand Master

+Zlip792 MVC

Posted
  • MVC
Posted
  On 12/10/2016 at 16:41, Gary7 said:

I moved up to Fx 50 Beta 6

 

ext_zpsxswfr7bp.png

Expand  

Only way could be to try by turning off addons one by one.

 

But you can review them from here - https://www.arewee10syet.com/

Grand Master

+Gary7 Subscriber²

Posted
  • Author
  • Subscriber²
Posted
  On 12/10/2016 at 16:46, Zlip792 said:

Only way could be to try by turning off addons one by one.

 

But you can review them from here - https://www.arewee10syet.com/

Expand  

I have every add on disabled and it still says disabled by addon

 

0/1 (Disabled by accessibility tools)

Grand Master

Brandon H Supervisor

Posted
  • Supervisor
Posted

it almost sounds like a profile corruption @Gary7 I would launch firefox from a run box with "Firefox.exe -p" to load the profile manager and try creating a new profile to see if that helps.

Grand Master

+Gary7 Subscriber²

Posted
  • Author
  • Subscriber²
Posted

I did a refresh of Firefox and it still did not work. I then looked at my profile folder and there were like 8 or 9 different profiles. I can't understand how Fx worked at all??

  On 12/10/2016 at 17:22, Circaflex said:

It is most likely an accessibility option that is causing e10s to be disabled.

 

about:config

 

search for accessibility and snip a screenshot and post it here. You can also force disable accessibility so it wont do that.

Expand  

 

acc.PNG

Grand Master

+Zlip792 MVC

Posted
  • MVC
Posted
  On 12/10/2016 at 17:37, Gary7 said:

I did a refresh of Firefox and it still did not work. I then looked at my profile folder and there were like 8 or 9 different profiles. I can't understand how Fx worked at all??

 

~snipped~

Expand  

Make following config to "accessibility.force_disabled" to 1 from 0.

Grand Master

+Zlip792 MVC

Posted
  • MVC
Posted
  On 12/10/2016 at 17:54, Gary7 said:

It was 0

Expand  

Make it to 1 and restart browser and check 'about:support', whether the Multi-Process is now enabled or not.

 

If enable then try to navigate neowin to check whether it is still causing issue or not.

Grand Master

Boo Berry

Posted
Posted

In about:config also make sure extensions.e10sBlocksEnabling and extensions.e10sBlockedByAddons are set to false too. Personally I also make sure browser.tabs.remote.force-enable and layers.offmainthreadcomposition.testing.enabled and browser.tabs.remote.autostart are all set to true (if they don't exist, create them as boolean). That forces e10s enabled for me.

Grand Master

Circaflex

Posted
Posted

all of the accessibility options need to be default, anything bold or userset will turn e10s off. You have many that are user set.

  On 12/10/2016 at 18:13, Gary7 said:

OK I have done all of that now how do I see if it is working?

Expand  

click the menu button and see if an option for new tabs is non-e10, or under settings multiprocess should be checked.

Grand Master

+Zlip792 MVC

Posted
  • MVC
Posted
  On 12/10/2016 at 18:13, Gary7 said:

OK I have done all of that now how do I see if it is working?

Expand  

Go to about:support to ensure that multi-process is 1/1.

This topic is now closed to further replies.
 Share
Go to topic listing