problem Problem Posting With Firefox

[+Gary7 Subscriber²]

Firefox is locking up on me about everytime I try to quote a member. I have to restart my machine to fix it. The problem is only with this site.

[+Zlip792 MVC]

Firefox version? Addons Installed? OS version?

 

Tried to clear cache and cookies? Ctrl + F5?

[Circaflex]

Working fine here, no such issues on Firefox stable, beta or nightly with e-10s.

[+Gary7 Subscriber²]

5 minutes ago, Zlip792 said:

Firefox version? Addons Installed? OS version?

 

Tried to clear cache and cookies? Ctrl + F5?

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.

[+Zlip792 MVC]

4 minutes ago, 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.

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.

[+Gary7 Subscriber²]

25 minutes ago, 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.

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

[+Zlip792 MVC]

7 minutes ago, Gary7 said:

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

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

 

 

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

[+Gary7 Subscriber²]

8 minutes ago, Zlip792 said:

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

 

 

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

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

[+Zlip792 MVC]

17 minutes ago, 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.

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?

[+Gary7 Subscriber²]

I moved up to Fx 50 Beta 6

 

[+Zlip792 MVC]

4 minutes ago, Gary7 said:

I moved up to Fx 50 Beta 6

 

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

 

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

[+Gary7 Subscriber²]

14 minutes ago, 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/

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

 

0/1 (Disabled by accessibility tools)

[+Gary7 Subscriber²]

It has this now though

 

[Circaflex]

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.

[Brandon H Supervisor]

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.

[+Gary7 Subscriber²]

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??

15 minutes ago, 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.

 

[+Zlip792 MVC]

14 minutes ago, 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~

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

[+Gary7 Subscriber²]

2 minutes ago, Zlip792 said:

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

It was 0

[+Zlip792 MVC]

1 minute ago, Gary7 said:

It was 0

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.

[Boo Berry]

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.

[+Gary7 Subscriber²]

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

[Circaflex]

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

Just now, Gary7 said:

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

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

[+Zlip792 MVC]

12 minutes ago, Gary7 said:

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

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

[+Gary7 Subscriber²]

OK Brandon Was right my profile is all corrupted. When I did Firefox - P everything was OK. Is there an easy way to fix this? @Brandon H

[Circaflex]

1 minute ago, Gary7 said:

OK Brandon Was right my profile is all corrupted. When I did Firefox - P everything was OK. Is there an easy way to fix this?

Create a new profile?