New issue
Advanced search Search tips

Issue 729430 link

Starred by 3 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Apr 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Flags regarding offline page reload behavior are being ignored

Reported by djsty...@gmail.com, Jun 5 2017

Issue description

UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.138 Safari/537.36 Vivaldi/1.8.770.56

Steps to reproduce the problem:
1. set "enable-offline-reload" to false and/or "enable-offline-reload-only-visible" to true.
2. restart chrome and restore previously opened tabs without internet access
3. enable internet access

What is the expected behavior?
The tabs shouldn't reload if "enable-offline-reload"==false.

If "enable-offline-reload-only-visible"==true then only the visible tab should be reload.

What went wrong?
When the Internet connection is established a lot of processes are being spawned for all the non-visible tabs. This leads to a huge memory and cpu load (see  Issue 393395 ).

It seems like the flags are being ignored. 

Did this work before? N/A 

Chrome version: 58.0.3029.68-1   Channel: beta
OS Version: Debian Testing
Flash Version: Shockwave Flash 999.999 r999

Debian Testing, amd64. Chromium beta 58.0.3029.68-1.
 
Labels: Needs-Triage-M58
Cc: rdsmith@chromium.org
Components: Internals>Network
Cc: ellyjo...@chromium.org mmenke@chromium.org
So the usual answer with flags is "they're experimental, don't count on them" and the right result of this bug might be to remove those flags; I think the experimentation around auto-reload is long in the past.  

Having said that, looking at the code, this should be working, and even if it wasn't, this sounds like the wrong default behavior (I thought we auto-reloaded only visible tabs by default).  

Elly, Matt: Am I right about default behavior?  Any awareness of changes that might have caused this?
I'm unaware of any changes.  Be great to investigate this, or at a minimum, at least remove the flag, but I'm not going to have time for it.
Status: Available (was: Unconfirmed)
Triager on duty. 

I agree that we should remove these experimental flags. I will send out a CL.
I looked at the code. This is more involved than removing an unused feature flag. I am marking this as available and moving it off triager's queue.
Cc: -rdsmith@chromium.org

Comment 8 by mmenke@chromium.org, Apr 25 2018

Status: WontFix (was: Available)
THe flag is actually enable-offline-auto-reload.  Sorry for the...erm...rather slow response.  :)

Sign in to add a comment