User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:54.0) Gecko/20100101 Firefox/54.0 Build ID: 20170127030206 Steps to reproduce: Open more one than Nightly tab. Actual results: When switching back to a fully loaded page, Nightly completely reloads the page. Expected results: Tabs should not reload when already loaded.
OS: Unspecified → Windows 10
Hardware: Unspecified → x86_64
I can't reproduce it with the latest Nightly. Did you test in safe mode and with a fresh profile?
Yes, I have since I know that's the first thing you ask about. I currently have this tab, my OUtlook tab, and my Yahoo tab open. When I tab between them, I get the little "I'm busy" rotating circle for anywhere from 5 to 45 seconds before the already loaded page loads again. With the fresh profile in safe mode, it isn't as bad as before though. If I tab back and forth quickly between two tabs, it doesn't happen. But if I do anything or look at the contents of one tab for a few seconds, then when I move to the next tab, it happens. I'm on a Toshiba L505 laptop with an AMD Turion II dual core processor and 4GB of memory. I'm running the 64-bit version of Win10 Professional.
[bugday-20170130] Does it happens frequently or sometimes only?
Quite often. It seems that the longer I stay on one page/tab, the longer it takes the other tab to reload when I switch to it. If I accidentally switch to an already loaded tab and quickly switch back to the previous tab, it doesn't happen. But if I remain on the second tab for anything more than a couple of seconds, when I switch back to the previous tab, it takes at least a few seconds for the first tab to reload.
User Agent: Mozilla/5.0 (Windows NT 6.3; Win64; x64; rv:54.0) Gecko/20100101 Firefox/54.0 I have tested your issue on latest Firefox release v51.0.1 and latest Nightly (Build ID: 20170201030207) and could not reproduce it. I have opened Outlook and Yahoo pages in two tabs and switched between them at different intervals. I did not observe the refresh event that you described. This issue is happening only with the 2 websites mentioned in comment 2? Or also with other websites? Are you using a cable connection or integrated Wi-Fi card or USB Wi-Fi card for internet connection?
No, it happens with Facebook, auto industry news sites, whatever I visit. I am using a Toshiba laptop. I have the integrated Wi-Fi card as well as an external antenna/Wi-Fi adapter. I don't think this should be a worry since the loaded pages are loaded.
Well, I am asking this because on PC I didn't see this issue. On my laptop from home I had the USB selective suspend mode ON and also the Wi-Fi power saving mode was ON. These to settings made my browsing experience a nightmare. I've turned them OFF and all was working as expected. These settings are under Control Panel->power Options->Edit Plan Settings . I know the pages are loaded but in this way we eliminate the hardware issues.
Marking this as Resolved - WFM due to the lack of response from the reporter and to the fact that I cannot reproduce the issue. If anyone can still reproduce it on latest versions, feel free to reopen the issue and provide more information.
Status: UNCONFIRMED → RESOLVED
Last Resolved: a year ago
Resolution: --- → WORKSFORME
And what were you waiting for a response from me on? I responded within hours to the ONLY request for further information that I received. I don't have any low power settings on my laptop. Everything is set for optimum performance. I have no idea what USB selective suspend mode is, but unless it defaults to on on a Toshiba laptop, it's off.
Status: RESOLVED → UNCONFIRMED
Resolution: WORKSFORME → ---
It might be a good idea to remember that not everybody is running equipment that's the newest latest and greatest. Many of us are lucky to have what we've got.
Mike, you could try to disable the USB selective suspend mode (The USB selective suspend feature allows the hub driver to suspend an individual port) and also Wi-Fi sleep settings. Here are the steps: https://goo.gl/KAKQw3 and https://goo.gl/15fSk1. We should eliminate all hardware related settings that may cause issues. Can you please retest this using latest FF release and latest Nightly build (https://nightly.mozilla.org/) and report back the results ?
I download and install Nightly builds as soon as they're pushed, so I have the latest build. I've had to minimize my usage of Nightly lately because of exactly that. Almost every site I go to in Nightly, the browser tells me the page wasn't opened because the page owner configured the site incorrectly and Nightly can't tell if the page is secure (or something like that.) What it means for me is that every site I use on a regular basis for my work, except one (http://sequoia.internetbrands.com/sequoia_v2/) is inaccessible to me. Yahoo. Gmail. Outlook. YouTube. Even my local library's page. Almost any site with secure transport is inaccessible because of this. The little I was able to do just playing around with a few site I could think of and ones I have pinned to the new tab page, disabling those two settings looks like it might have helped some, although the USB setting was already disabled.
That is pretty strange. The websites that are not working in Nightly are working in other browsers, like Chrome or IE/Edge? For me all websites that you mentioned in Comment 12 are loading and working properly. I cannot reproduce this issue. Here are some articles from Mozilla Support that may help you in debugging the webpages not loading issue: https://goo.gl/4uaLO2, https://goo.gl/4xkP0d and https://goo.gl/lCSlDH . Can you please retest this using latest Nightly build after the latest changes to your settings and report back the results? When doing this, please use a new clean Firefox profile, maybe even safe mode, to eliminate custom settings as a possible cause (https://goo.gl/AR5o9d).
Created attachment 8839212 [details] "Unsecure sites" screenshot Screenshot of what I get when I try and go to Yahoo Mail.
Ok. Again, I'm on the latest Nightly build. The Firefox/Mozilla KB is useless in solving this problem. As long as the page isn't secure, I can visit it. All of my webmail accounts are working perfectly in everything but Nightly. I haven't checked Firefox yet. This means that testing the original problem is a real pain in the ass for me. Considering that I can't do ANY work in Nightly anymore, I've only been using it to see if you've made any changes that would allow me to get back to work. I hate Edge and some of my work sites aren't coded for Chrome, so I'm stuck with Edge until you fix this latest one.
Well, the screenshot from comment 14 is not from a clean profile or safe mode. I can see that there are add-ons installed. What add-ons are installed on that profile? Antivirus products may cause this. Please try this in Safe Mode (https://goo.gl/AR5o9d). I cannot reproduce this state and it is more of a system issue than an issue with Nightly. Also, please go to about:support -> Copy text to clipboard -> paste it into a document and attach it to this bug so I can see what add-ons and antivirus you have, to narrow down the issue. In case you get this problem on multiple unrelated HTTPS-sites, it indicates that something on your system or network is intercepting your connection and injecting certificates in a way that is not trusted by Firefox. (https://goo.gl/KHEQ8f)
Just had another update pushed to me. Same thing happening. Add-ons enabled or disabled. Also turned off my Kaspersky to check Yahoo and Outlook. Same thing.
I would suggest to open a new bug for the issue related to the Security Certificate. This issue seems to be related to something that is specific to your setup, could you please try to find a regression range using Mozregression tool? Information on the tool is available at http://mozilla.github.io/mozregression/. Please don't hesitate to contact us if you encounter any problems. For the main issue I will assign a possible related component.
Component: Untriaged → DOM: Content Processes
Product: Firefox → Core
Ok. Will do. Thanks Vlad.
Status: UNCONFIRMED → RESOLVED
Last Resolved: a year ago → 8 months ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.