Google search page functions broken.
When I go to google.com and do a search the results page has the "tools" button but it does not work. The "people also ask" categories are also broken (they will not expand), and, if I click the "images" filter button to view images associated with my search it either shows no images (or only a few images) and a bunch of blank boxes. I have found that if I hold the shift key and click the reload button everything is back and working properly until the next time I do a google.com search, then it is back to the same odd behavior. So, my assumption here is that either a cookie or some site data is corrupting the results page for my search. Running Firefox 92.0 (64-bit) on a Windows 7 Dell machine and everything was working fine until about two months ago. Also, Chrome does not show the same behavior. BTW. I have also done everything I have found that was recommended to fix Firefox issues with Google search. Run Firefox in private mode, run without plugins, changed themes, created new profile, I even completely uninstalled Firefox and did a clean install all with the same results. Any help is appreciated. It is almost got me ready to move back to Chrome.
Gekozen oplossing
Was that with the Norton enabled or disabled? It's still trying and failing to make a conduit to SymBfw.js (Ah, Sym for Symantec), plus "XHRGET https://ratings-wrs.norton.com/brief?url=https://www.google.com/search". I no longer think that's your problem, but if it was supposed to be disabled/uninstalled when you recorded this we should look into why those two things are still happening. Separate question though!
Thank you very much for this detailed log. The one thing that jumps out at me is that the initial request uses HTTP/3 and the shift-reload falls back to HTTP/2. I'm not confident this is an important difference: my own browser does this and I'm not seeing the problem. This could explain why Shift-reload made a difference even though the cache clearly didn't.
The script it's failing on is the first and biggest chunk of application script so it's easy to see why the page is broken after that point. not much clue why it broke in the first place :-( Could Norton beinterfering with HTTP/3 somehow, external to the browser? A proxy, maybe? I know those anti-virus products like to inspect network traffic so it's conceivable, but Norton is so popular that surely we'd have plenty of reports by now if that were the case. Clearly _some_ HTTP/3 is getting through because the page loaded enough to start loading the scripts.
All that to say: let's try disabling HTTP/3 and see if that fixes your problem, but it might not. You can live without HTTP/3 -- all the sites that support it fall back to support older browsers
1. open the advanced preference page about:config. Agree to be careful if asked 2. type http3 in the filter box 3. double-click network.http.http3.enabled to set it to false
How long did you say you've had this problem? We shipped HTTP/3 in Release versions around April or May 2021.
Dit antwoord in context lezen 👍 0Alle antwoorden (6)
dveditz: moz-extension://0bd18f96-ba4b-47f9-b2f6-04c696bea458 = id=nortonsafeweb@symantec.com, name="Norton Safe Web" (disabling Norton Safe Web extension does not fix the issue).
Disk cache = false ... no help Memory cache = false ... no help Either one by itself and both at the same time = no help Both = false and Norton Safe Web off (I even tried it after removing Norton Safe Web) = no help
- FROM THE BROWSER CONSOLE WITH XHR AND REQUESTS TURNED ON FROM AN INITIAL SEARCH (THE PROBLEM IS PRESENT):
NS_ERROR_NOT_AVAILABLE: Component returned failure code: 0x80040111 (NS_ERROR_NOT_AVAILABLE) [nsIDocShell.domWindow] browsing-context.js:403
GET https://www.google.com/search?q=dogs&btnK=Google+Search&source=hp&ei=KYM7YaSMEcWa-AaSl7LwAQ&iflsig=ALs-wAMAAAAAYTuROSxTcEJrehAtBqbM_5YPiyPrWZkJ [HTTP/3 200 OK 955ms]
AbortError: Actor 'Conduits' destroyed before query 'RuntimeMessage' was resolved ConduitsParent.jsm:297 Unchecked lastError value: Error: Could not establish connection. Receiving end does not exist. 3 SymBfw.js:115
GET https://www.google.com/images/branding/googlelogo/2x/googlelogo_color_92x30dp.png
GET https://fonts.gstatic.com/s/googlesans/v14/4UaGrENHsxJlGDuGo1OIlL3Owp4.woff2
XHRGET https://ratings-wrs.norton.com/brief?url=https://www.google.com/search [HTTP/1.1 200 OK 33ms]
GET https://www.gstatic.com/ui/v1/activityindicator/loading_24.gif
GET https://www.google.com/images/nav_logo321_hr.webp [HTTP/3 200 OK 0ms]
GET https://id.google.com/verify/AHGvNoyu8oexf6f0QsQ1QFyCvEUpdXXxYXcNlOIBU1qQqYwS-WddPQ72nPvNo6IpJ1x3-8mdEF5pelqFsQe33yHJvDP3-GNYS0T_jwRHQTkZaKqqapj6IQ [HTTP/3 204 No Content 63ms]
POST https://www.google.com/gen_204?s=web&t=aft&atyp=csi&ei=MoM7YZDQO4mv5NoPsL-O-AQ&rt=wsrt.259,aft.751,prt.735,sct.676&imn=37&ima=2&imad=2&aftp=609&bl=luCR [HTTP/3 204 No Content 40ms]
GET https://www.google.com/favicon.ico [HTTP/3 200 OK 0ms]
Loading failed for the <script> with source “https://www.google.com/xjs/_/js/k=xjs.s.en_US.FOdRiDfL8xk.O/am=QnAAgAAAAAAAAPgHAL1CICMIBAAAAJgBBAAAAAAQACEAAhLvJiYAAAABAGVeAhgAAAABQIMAMIcAIHEABQABLAACAAAAHIF9AM4fAMAjWMIFAAAAAAAAAtASzFABiYAAIAAAAACI1QRVfQABAEQ/d=1/ed=1/dg=2/rs=ACT90oHU4uNMrD0BkFGRDQnl7zTWjxmVFg/m=attn,cdos,cr,dpf,hsm,jsa,d,csi”. search:1:1
Continued on next post...
- FROM THE BROWSER CONSOLE WITH XHR AND REQUESTS TURNED ON AND AFTER SHIFT/RELOAD (THE PROBLEM IS FIXED):
AbortError: Actor 'Conduits' destroyed before query 'RuntimeMessage' was resolved ConduitsParent.jsm:297 Unchecked lastError value: Error: Could not establish connection. Receiving end does not exist. 2 SymBfw.js:115
GET https://fonts.gstatic.com/s/googlesans/v14/4UaGrENHsxJlGDuGo1OIlL3Owp4.woff2 [HTTP/2 200 OK 108ms]
XHRGET https://ratings-wrs.norton.com/brief?url=https://www.google.com/search [HTTP/1.1 200 OK 382ms]
GET https://www.google.com/images/branding/googlelogo/2x/googlelogo_color_92x30dp.png [HTTP/2 200 OK 35ms]
GET https://www.google.com/images/searchbox/desktop_searchbox_sprites318_hr.webp [HTTP/2 200 OK 37ms]
GET https://www.gstatic.com/ui/v1/activityindicator/loading_24.gif [HTTP/2 200 OK 83ms]
GET https://id.google.com/verify/AHGvNowxDnmfX5hbksmTC-f4qzBflwuyTVofCeV3Xw1VTsGoi163T1TAUybS2GDLPVpq0yu8jS-kOGgz9CjAznh85JSAt_wb_Hn4wSULLQoQOsNDQsPYs9M [HTTP/2 204 No Content 277ms]
GET https://www.google.com/images/nav_logo321_hr.webp [HTTP/2 200 OK 40ms]
POST https://www.google.com/gen_204?s=web&t=aft&atyp=csi&ei=-4Q7Yb3GGKHQ5NoP_MSesA0&rt=wsrt.154,aft.884,prt.871,sct.802&imn=51&ima=5&imad=5&aftp=609&r=1&bl=luCR [HTTP/2 204 No Content 60ms]
GET https://www.google.com/favicon.ico [HTTP/2 200 OK 20ms]
XHRGET https://www.google.com/complete/search?q&cp=0&client=gws-wiz&xssi=t&hl=en&authuser=0&pq=dogs&psi=-4Q7Yb3GGKHQ5NoP_MSesA0.1631290625164&ofp=GO79rMr_4MDFHhjzt4_ZvbXN1oUBGI6ntZLtmL-a_wEY9Oq0lNbc-OTcARjU0K2F1pSf2LkB&nolsbt=1&dpr=1.25 [HTTP/2 200 OK 220ms]
XHRGET https://www.google.com/complete/search?q=dogs&cp=0&client=desktop-gws-wiz-on-focus-serp&xssi=t&hl=en&authuser=0&pq=dogs&psi=-4Q7Yb3GGKHQ5NoP_MSesA0.1631290625164&ofp=GO79rMr_4MDFHhjzt4_ZvbXN1oUBGI6ntZLtmL-a_wEY9Oq0lNbc-OTcARjU0K2F1pSf2LkBEAE&dpr=1.25 [HTTP/2 200 OK 60ms]
GET https://www.google.com/images/icons/material/system/1x/email_grey600_24dp.png [HTTP/2 200 OK 40ms]
GET https://www.gstatic.com/kpui/social/twitter_32x32.png [HTTP/2 200 OK 20ms]
GET https://www.gstatic.com/kpui/social/fb_32x32.png [HTTP/2 200 OK 20ms]
GET https://www.gstatic.com/og/_/ss/k=og.qtm.OMLc9o8cUD0.L.F4.O/m=qcwid/excm=qaaw,qadd,qaid,qein,qhaw,qhbr,qhch,qhga,qhid,qhin,qhpr/d=1/ed=1/ct=zgms/rs=AA2YrTv9lvCN1y9XI5K_uhzGN3NO-1fAwg [HTTP/2 200 OK 60ms]
GET https://www.gstatic.com/og/_/js/k=og.qtm.en_US.Wg3khvZzf3k.O/rt=j/m=qabr,q_d,qcwid,qapid/exm=qaaw,qadd,qaid,qein,qhaw,qhbr,qhch,qhga,qhid,qhin,qhpr/d=1/ed=1/rs=AA2YrTu-OtI5_E9WfPOTd89qO_VyPD3HSw [HTTP/2 200 OK 60ms]
POST https://www.google.com/gen_204?atyp=i&r=0&ei=-4Q7Yb3GGKHQ5NoP_MSesA0&ct=kptm:il&iw=1111&ih=588&sh=864&sw=1536&tmw=368&tmh=155&nvi=4&eg=0&zx=1631290625340 [HTTP/2 204 No Content 40ms]
GET https://apis.google.com/_/scs/abc-static/_/js/k=gapi.gapi.en.7RphtNcGHDQ.O/m=gapi_iframes,googleapis_client/rt=j/sv=1/d=1/ed=1/rs=AHpOoo_-zmYhp_Ir7_CCxM3l-AckMvaI9A/cb=gapi.loaded_0 [HTTP/2 200 OK 117ms]
GET https://i.ytimg.com/vi/MPV2METPeJU/mqdefault.jpg?sqp=-oaymwEECHwQRg&rs=AMzJL3kQ2oFMiuSEoNuPOKpGEsqMqAPDJA [HTTP/2 200 OK 355ms]
GET https://i.ytimg.com/vi/5pLCmLgjiJ8/mqdefault.jpg?sqp=-oaymwEECHwQRg&rs=AMzJL3kiOaz_sgRdh1OK4Ta7nowNahYrZw [HTTP/2 200 OK 305ms]
GET https://i.ytimg.com/vi/IACqfc8BtK4/mqdefault.jpg?sqp=-oaymwEECHwQRg&rs=AMzJL3mNGwGVhk5F9W_hvbcabaQq4_5WHg [HTTP/2 200 OK 305ms]
XHRGET https://www.google.com/client_204?cs=1 [HTTP/2 204 No Content 60ms]
XHRGET https://www.google.com/async/bgasy?ei=-4Q7Yb3GGKHQ5NoP_MSesA0&yv=3&async=_fmt:jspb [HTTP/2 200 OK 80ms]
GEThttps://encrypted-tbn0.gstatic.com/images?q=tbn:ANd9GcTWBGhsj92F2N32Ychgd9nbQe4581kRmGMd33xJiNiA9A&s[
I also have the Web Developer Tools Console logs of the same events but they are really long. If you need them I can post as multiple replies.
Thanks so much for your time and expertise.
Gekozen oplossing
Was that with the Norton enabled or disabled? It's still trying and failing to make a conduit to SymBfw.js (Ah, Sym for Symantec), plus "XHRGET https://ratings-wrs.norton.com/brief?url=https://www.google.com/search". I no longer think that's your problem, but if it was supposed to be disabled/uninstalled when you recorded this we should look into why those two things are still happening. Separate question though!
Thank you very much for this detailed log. The one thing that jumps out at me is that the initial request uses HTTP/3 and the shift-reload falls back to HTTP/2. I'm not confident this is an important difference: my own browser does this and I'm not seeing the problem. This could explain why Shift-reload made a difference even though the cache clearly didn't.
The script it's failing on is the first and biggest chunk of application script so it's easy to see why the page is broken after that point. not much clue why it broke in the first place :-( Could Norton beinterfering with HTTP/3 somehow, external to the browser? A proxy, maybe? I know those anti-virus products like to inspect network traffic so it's conceivable, but Norton is so popular that surely we'd have plenty of reports by now if that were the case. Clearly _some_ HTTP/3 is getting through because the page loaded enough to start loading the scripts.
All that to say: let's try disabling HTTP/3 and see if that fixes your problem, but it might not. You can live without HTTP/3 -- all the sites that support it fall back to support older browsers
1. open the advanced preference page about:config. Agree to be careful if asked 2. type http3 in the filter box 3. double-click network.http.http3.enabled to set it to false
How long did you say you've had this problem? We shipped HTTP/3 in Release versions around April or May 2021.
dveditz: The logs were all with both the disk and memory cache enabled and Norton Safe Web turned on. The good news, I guess at least for me, disabling HTTP/3 in Firefox fixes the issue. The searches are complete, the page loads fully, the Tools button functions, the People Also Ask lines expand on request, and the Images page loads all the images. Yeah!! I see nothing in Norton that I feel would interfere with HTTP/3, at least not on the surface, I do not know about under the hood. Norton is set to auto-configure the proxy setting and by that I assume it means it follows the Windows proxy settings. I first noticed the problem about 8 or 10 weeks back (I can't remember exactly when) but that doesn't mean I didn't have the issue before then. You deserve a salary raise as you surely know your stuff and I want to thank you very much for all the time and energy you have put into my problem (thanks to everyone that helped!). I will mark this problem solved. Again, Thanks to all that helped.
Great, glad that solved it for you!
One of the problems releasing networking protocol improvements (not just HTTP/3) is that "the internet" is a wide mix of hardware and software, and an unfortunate amount of old stuff mishandles anything new and unexpected no matter how carefully the new specifications build within the bounds of existing specifications. Since HTTP was created in 1991, HTTP/3 is the first version that uses UDP packets instead of TCP packets. Shouldn't be a problem: UDP is used all over the place such as for DNS and Zoom/WebEx/etc video conferencing. But, in practice...
I'm sure you're right it's not Norton: we'd have a lot more reports like this and it'd be easy to finger as the common factor. Much more likely some piece of old hardware on the wire between you and Google servers.
I agree about the hardware between me and the www. I have been looking for UDP blocking (or something akin to that) in the Norton firewall, my router and my cable modem but I have not found anything that jumps out at me as the culprit. I guess I just live without HTTP/3 until I really need it or circumstances force the issue on me. Thanks again.