Avatar for Username

Vyhľadajte odpoveď

Vyhnite sa podvodom s podporou. Nikdy vás nebudeme žiadať, aby ste zavolali alebo poslali SMS na telefónne číslo alebo zdieľali osobné informácie. Nahláste prosím podozrivú aktivitu použitím voľby “Nahlásiť zneužitie”.

Ďalšie informácie

Táto téma bola archivovaná. Ak potrebujete pomôcť, založte prosím novú otázku.

Firefox 50.1.0 unable to handle webpage with embedded g-map

  • 1 odpoveď
  • 3 majú tento problém
  • 1 zobrazenie
  • Posledná odpoveď od 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 !

Všetky odpovede (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.