Rechercher dans l’assistance

Évitez les escroqueries à l’assistance. Nous ne vous demanderons jamais d’appeler ou d’envoyer un SMS à un numéro de téléphone ou de partager des informations personnelles. Veuillez signaler toute activité suspecte en utilisant l’option « Signaler un abus ».

En savoir plus

Firefox 58.0.2 freezes up on www.google.com

more options

At two locations with Windows 10 1709 firefox freezes when on www.google.com Keyboard and mouse become unresponsive and I have to end task to close firefox.

I disabled the eset antivirus, reinstalled firefox after clearing the appdata sections and registry entries. I used system restore on one machine and reformatted with an acronis image; back a week.

This occurs when I am not signed into google or firefox accounts or when I use a private window. No other pages, apps or browsers have this problem. The two machines are very different and in different locations.

At two locations with Windows 10 1709 firefox freezes when on www.google.com Keyboard and mouse become unresponsive and I have to end task to close firefox. I disabled the eset antivirus, reinstalled firefox after clearing the appdata sections and registry entries. I used system restore on one machine and reformatted with an acronis image; back a week. This occurs when I am not signed into google or firefox accounts or when I use a private window. No other pages, apps or browsers have this problem. The two machines are very different and in different locations.

Solution choisie

Thank you Jscher2000! That works.

If you are in a position to advise google, please ask them to knock it off! My machines are very powerful and I wasted a whole day with four resources, google works, microsoft, eset and firefox... and I reinstalled, and reformatted with an image backup. For me to use google as my go to source, they really need to be more careful with the gimicks.

But thank you for your great answer.

Lire cette réponse dans son contexte 👍 0

Toutes les réponses (6)

more options

There is a Valentine's day thing going on on the home page that consumes a lot of resources (judging from how it spins up my fan). Try starting on a different page for today, such as a search results page:

https://www.google.com/search?q=firefox

more options

Solution choisie

Thank you Jscher2000! That works.

If you are in a position to advise google, please ask them to knock it off! My machines are very powerful and I wasted a whole day with four resources, google works, microsoft, eset and firefox... and I reinstalled, and reformatted with an image backup. For me to use google as my go to source, they really need to be more careful with the gimicks.

But thank you for your great answer.

more options

I'm getting my companies mixed up. JSCHER2000.

I wonder if someone on this forum who is in touch with firefox can look into why firefox is unresponsive on todays valentinve google search at www.google.com. Other browsers seem immuned. perhaps mozilla can figure out what has happened so it doesn't repeat. Particularly if high resource pages become the thing in the future. Thanks.

more options

Here is some more discussion of this problem. Google's code is notoriously complex, so I don't know if anyone is going to invest the time to figure out what's special about this animation if we're never going to see it again...

https://www.reddit.com/r/firefox/comments/7xh702/todays_google_doodle_is_using_100_gpu_quantum/

more options

Well, Firefox worked perfectly when the valentine animation was taken down and now something has replaced it and Firefox is freezing again on www.google.com I ended the task and moved to duckduckgo.com I have two computers, win 10 that have reasonable processors and ram, it will be reasonable to ask Mozilla to recon why other browsers are not freezing up rather than trying to prevent Google or other sites from loading down their pages with memory hogging animation. I just haven't got a clue how Mozilla will become aware of the browsers apparent shortcoming.

more options

Today's Google home page "doodle" was reported on the "Web Compatibility" site with a link to the doodle archive, so hopefully that will stay available long enough for people to understand what it's doing: https://webcompat.com/issues/15483