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.

Avatar for Username

Search Support

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.

Learn More

This thread was archived. Please ask a new question if you need help.

Firefox 50.1.0 unable to handle webpage with embedded g-map

  • 1 reply
  • 3 have this problem
  • 1 view
  • Last reply by Oxylatium

AnirF
AnirF
more options

I am a firefox user of more than a decade. sadly, Firefox 50.1.0 gives horrendous performance after nagging me for a week to upgrade.

It goes into a loop of "A webpage is slowing you down, what do you want to do". Even after that webpage is closed it is unable to recover and has to be restarted every time. the webpage is 99acres.com > map search. before the upgrade it was running fine.

even other pages take a long time to appear after they have been loaded. Every time I move between tabs, pages that have already loaded show a "processing" icon for few seconds before appearing.

I have been forced to use chrome, 50.1.0 performs worse than what IE did back in the 90's !

I am a firefox user of more than a decade. sadly, Firefox 50.1.0 gives horrendous performance after nagging me for a week to upgrade. It goes into a loop of "A webpage is slowing you down, what do you want to do". Even after that webpage is closed it is unable to recover and has to be restarted every time. the webpage is 99acres.com > map search. before the upgrade it was running fine. even other pages take a long time to appear after they have been loaded. Every time I move between tabs, pages that have already loaded show a "processing" icon for few seconds before appearing. I have been forced to use chrome, 50.1.0 performs worse than what IE did back in the 90's !

All Replies (1)

Oxylatium
Oxylatium
more options

Do you have multiprocess (e10s) enabled? Type about:support and read the line "multi-process".

If that's the case, disable e10s in about:config: browser.tabs.remote.autostart = false (restart) and make a test.