Address bar stops working after a while until firefox restart with Avast installed
Categories
(External Software Affecting Firefox :: Other, defect)
Tracking
(Not tracked)
People
(Reporter: stfrancia.ce, Unassigned)
References
Details
Attachments
(6 files)
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:129.0) Gecko/20100101 Firefox/129.0
Steps to reproduce:
I open Firefox, alt-tab out of that screen back into whatever I was doing. Minutes later (possibly 20-30) the issue arises.
Actual results:
The address bar will no longer 'search' anything. Pressing enter will make it submit the query but it doesn't redirect you to the results page. Creating a new tab or new window or reloading the page does nothing. This behaviour will persist until I restart Firefox by closing every tab and opening it again.
Actually in the middle of this report, I tried to Google what a user agent string is with Right Click > Search Google for "user agent string" and that also doesn't work.
Expected results:
Entering a query or trying to search with Google should redirect you to the Google results page.
|
||
Comment 1•1 year ago
|
||
The Bugbug bot thinks this bug should belong to the 'Firefox::Address Bar' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
SImilar issue. 129.0.1 (64 bit). Using @bing or @wikepedia works, but @google does not.
stfrancia and Jim, please follow these steps to help Mozilla investigate this:
- Go to the Troubleshooting Information page
- Click
Copy text to clipboard - Paste it into Notepad and save it
- Use this button to upload your file: screenshot
|
Reporter | |
Comment 5•1 year ago
|
||
Experiencing a similar problem.
Randomly, when opening a new tab, the address bar seems to stop working.
new tab is set to open to blank page, and if i try to search something, the query string gets created, eg https://www.google.com/search?q=foo but nothing loads.
problem persists even when closing that specific new tab and opening a new one.
opening another page via a bookmark seems to work tho.
Mark, please look into this. This issue is making Firefox unusable for some people, and the triage owner is on vacation.
|
||
Comment 8•1 year ago
|
||
When this happens, can someone please take a look at the Browser Console and see if there are any errors/warnings and post them here in an attachment?
You can access the Browser Console via the three-bar menu -> More Tools -> Browser Console.
|
|
||
Updated•1 year ago
|
18:00:52.088
SearchSuggestionController found an unexpected string value: HTTP error 15 SearchSuggestionController.sys.mjs:645:17
18:07:27.642 <empty string> 2
23:15:34.754 SearchEngine: getSubmission: searchTerms is empty! 5 SearchEngine.sys.mjs:1428:23
09:35:16.072
URLBar - MerinoClient [HNT_WEATHER_FEED]: Fetch error: TypeError: NetworkError when attempting to fetch resource. 3 MerinoClient.sys.mjs:278:25
09:35:16.931
Sync encountered an error - see about:sync-log for the log file. policies.sys.mjs:972:15
09:55:26.508
Cookie warnings 6
09:55:38.306 Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://waa-pa.clients6.google.com/$rpc/google.internal.waa.v1.Waa/Ping. (Reason: CORS request did not succeed). Status code: (null).
09:55:43.433 Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://waa-pa.googleapis.com/$rpc/google.internal.waa.v1.Waa/Ping. (Reason: CORS request did not succeed). Status code: (null).
09:56:03.553 Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://waa-pa.clients6.google.com/$rpc/google.internal.waa.v1.Waa/Ping. (Reason: CORS request did not succeed). Status code: (null).
09:56:04.686 Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://waa-pa.googleapis.com/$rpc/google.internal.waa.v1.Waa/Ping. (Reason: CORS request did not succeed). Status code: (null).
10:05:28.840 Warning: attempting to write 6979 bytes to preference browser.topsites.contile.cachedTiles. This is bad for general performance and memory usage. Such an amount of data should rather be written to an external file. 2
10:25:42.678 Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://waa-pa.clients6.google.com/$rpc/google.internal.waa.v1.Waa/Ping. (Reason: CORS request did not succeed). Status code: (null).
10:25:44.694 Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://waa-pa.googleapis.com/$rpc/google.internal.waa.v1.Waa/Ping. (Reason: CORS request did not succeed). Status code: (null).
10:26:06.272 Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://waa-pa.clients6.google.com/$rpc/google.internal.waa.v1.Waa/Ping. (Reason: CORS request did not succeed). Status code: (null).
10:26:08.288 Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://waa-pa.googleapis.com/$rpc/google.internal.waa.v1.Waa/Ping. (Reason: CORS request did not succeed). Status code: (null).
10:30:43.034 Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://waa-pa.clients6.google.com/$rpc/google.internal.waa.v1.Waa/Ping. (Reason: CORS request did not succeed). Status code: (null).
10:30:44.886 Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://waa-pa.googleapis.com/$rpc/google.internal.waa.v1.Waa/Ping. (Reason: CORS request did not succeed). Status code: (null).
10:31:06.643 Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://waa-pa.clients6.google.com/$rpc/google.internal.waa.v1.Waa/Ping. (Reason: CORS request did not succeed). Status code: (null).
10:31:08.659 Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://waa-pa.googleapis.com/$rpc/google.internal.waa.v1.Waa/Ping. (Reason: CORS request did not succeed). Status code: (null).
|
|
||
Comment 10•1 year ago
|
||
A couple of thoughts. Are the date/time on your machines set correctly?
If you temporarily disable Avast (specifically the internet protection parts), does that recover the situation?
|
||
Comment 11•1 year ago
|
||
Date/Time appears to be set accurately. Sync'd to server.time.windows.com at 12:06AM today.
Turned off Avast. Will post console if search problem reoccurs. Note that this problem is not continuous. It occurs randomly and disappears at random.
|
||
Comment 12•1 year ago
|
||
(In reply to Mark Banner (:standard8) from comment #8)
When this happens, can someone please take a look at the Browser Console and see if there are any errors/warnings and post them here in an attachment?
You can access the Browser Console via the three-bar menu -> More Tools -> Browser Console.
I got
Error: Form history is disabled, only remove operations are allowed
update resource://gre/modules/FormHistory.sys.mjs:1080
addToFormHistory resource:///modules/UrlbarUtils.sys.mjs:1114
pickResult resource:///modules/UrlbarInput.sys.mjs:1204
pickElement resource:///modules/UrlbarInput.sys.mjs:921
handleNavigation resource:///modules/UrlbarInput.sys.mjs:667
handleCommand resource:///modules/UrlbarInput.sys.mjs:604
handleKeyNavigation resource:///modules/UrlbarController.sys.mjs:345
_on_keydown resource:///modules/UrlbarInput.sys.mjs:4161
maybeDeferEvent resource:///modules/UrlbarEventBufferer.sys.mjs:159
_on_keydown resource:///modules/UrlbarInput.sys.mjs:4160
handleEvent resource:///modules/UrlbarInput.sys.mjs:568
|
|
||
Comment 13•1 year ago
|
||
added as an attachment.
|
||
Comment 14•1 year ago
•
|
||
(In reply to Joshua from comment #12)
Error: Form history is disabled, only remove operations are allowed
update resource://gre/modules/FormHistory.sys.mjs:1080
addToFormHistory resource:///modules/UrlbarUtils.sys.mjs:1114
This should be innocuous, if addToFormHistory throws we just print an error to the console and move on. It won't affect navigation.
In the previous logs there seem to be network problems, as the SearchSuggestionController, Merino (and maybe Sync) are reporting to be unable to reach the network.
As an antivirus may intercept traffic, it may effectively cause this kind of issues, especially for specific browsers if their network stack implementation differs.
|
|
||
Comment 15•1 year ago
|
||
The indications at the moment are that it is Avast that is potentially causing the issue - as it seems to be more network connections than just the address bar.
Therefore moving this to the external software affecting Firefox, as I think that's the better place to continue triage.
|
|
||
Comment 16•1 year ago
|
||
Just had an answer from one of the support threads:
I eventually tried Standard8's suggestion, disable Avast AV. Had it disabled for close on 5hrs and have been
browsing at various times WITHOUT any issues!Took a look at the Avast forum and what do you know, others having the same or similar issues running both on the latest versions. Seems that no one from Avast has picked up on the problem though! Anyway my understanding is now that it's Avast's Webshield that's the culprit and it's affecting Google searches along with Gmail reporting no connection and Error #001. No idea why it should be so random in the problems it causes. So currently I've re-enable Avast's shields with the exception of the Webshield.
I can't see the reference on the forums, :gstoll do we have an Avast contact that we could try point this out to?
|
||
Comment 17•1 year ago
•
|
||
QA managed to reproduce this issue on Firefox 129.0.2 on Windows 10. Please note that the issue is intermittent, and it seems to happen after a brief idle period.
- Windows version: Version 22H2 (OS Build 19045.2846)
- Avast Free Antivirus version: 24.8.6127 ( build 24.8.9372.864)
- Default search engine: Google
- Dual screen setup( HDMI Dell connected to the testing station)
Attaching the about:support and browser console logs. Please let us know if there’s anything else we can provide, thank you.
|
|
||
Comment 19•1 year ago
|
||
There's a workaround being posted about setting
security.tls.enable_0rtt_data
to false.
however, i won't vouch for it, since i personally don't know what it does specifically.
maybe someone from the firefox side can shed some light.
it does probably beat navigating the internet without an AV on tho
|
|
||
Comment 20•1 year ago
|
||
Even if it's likely to be a bug in Avast, it may be of interest for our networking team, even just as an heads-up.
|
||
Comment 21•1 year ago
|
||
Similar issue since few days.
After few mins unable to launch search from adress bar.
Restart FF solve temporary the issue.
|
|
Reporter | |
Comment 22•1 year ago
|
||
Have had to revert back to Chrome but will try to set security.tls.enable_0rtt_data to false and use Firefox again for a bit. I'll report back if it works.
|
|
Reporter | |
Comment 23•1 year ago
|
||
Haven't closed Firefox in about 5 hours now. Turning off security.tls.enable_0rtt_data definitely works.
|
||
Comment 24•1 year ago
|
||
I've had this for a few weeks, it works if you type in the search words again.
Where is the 'security.tls.enable_0rtt_data' setting - somewhere in the reg?
|
||
Comment 27•1 year ago
|
||
Let me try to get contact info for someone at Avast. For reference, here are some relevant Avast support forum threads: thread 1, thread 2.
|
|
||
Comment 28•1 year ago
|
||
(In reply to Greg Stoll :gstoll from comment #27)
Let me try to get contact info for someone at Avast. For reference, here are some relevant Avast support forum threads: thread 1, thread 2.
seems like they issued a hotfix
To quote the post:
"This hotfix should get installed automatically, but you can also follow the steps below to ensure it's applied:
Open Avast and go to - Menu - Settings - General - Update.
Click the second CHECK FOR UPDATES button.
Restart your computer.
Open Avast and go to - Menu - About Avast
Ensure that the last 3 digits of the build number read "865" or "866" (see the attached screenshot)
Open your web browser and try to replicate the problem."
|
|
||
Comment 29•1 year ago
•
|
||
Thanks for the info! From the forum thread it sounds like people are reporting that this fixes the problem; let's leave this bug open for a bit to be sure.
|
|
||
Comment 30•1 year ago
|
||
Another user on Reddit indicates that the hotfix fixed their problem.
I'm going to resolve this bug since it seems like as the hotfix gets rolled out, the issue will go away.
|
||
Updated•1 year ago
|
Description
•