mail.google.com not responding
Categories
(Core :: Networking, defect)
Tracking
()
People
(Reporter: xynton, Unassigned)
Details
User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:106.0) Gecko/20100101 Firefox/106.0
Steps to reproduce:
Start FF, wait some minutes (varies but not more than 30, mostly about 5-10), try to start mail.google.com or, if it is already running, make any action with letters.
Actual results:
Indicator shows that site start loading but nothing happens and after a ~1 min load indicators stops too. If google mail is already running it is not responded: no actions is possible with acc (can't read/remove letters, change settings, even log out); clicking on any link just activate loading indicator but nothing happens. BUT: if I start any VPN it works normally. OR: if I open "about:networking#logging" and start logging it works normally too. NOTE: I running "no java script" version of mail.
Expected results:
Site loads, letters can be managed.
|
||
Comment 1•3 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::Networking' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
Thanks for the report.
Are you able to reproduce with http logs? You may want to email logs to necko@mozilla.com in case of personal data concerns.
(In reply to Ed Guloien [:edgul] from comment #2)
Thanks for the report.
Are you able to reproduce with http logs? You may want to email logs to necko@mozilla.com in case of personal data concerns.
No; the turning logging on IS the method to resolve the issue. :D
|
||
Comment 4•3 years ago
|
||
I tried to reproduce this issue on our side but without success, mail.google.com page loads without issues even after 10 to 15 minutes of being idle.
|
||
Comment 5•2 years ago
|
||
(In reply to xynton from comment #3)
(In reply to Ed Guloien [:edgul] from comment #2)
Thanks for the report.
Are you able to reproduce with http logs? You may want to email logs to necko@mozilla.com in case of personal data concerns.
No; the turning logging on IS the method to resolve the issue. :D
Sorry, without the enough information, there is not much we can do here.
I'd like to close this bug for now. Feel free to reopen this bug when you have more information (http log) to share. Thanks.
Description
•