Project: chromium Issues People Development process History Sign in
New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.
Starred by 315 users
Status: WontFix
Owner: ----
Closed: Aug 2012
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Feature

Blocking:
issue 153544

Restricted
  • Only users with Commit permission may comment.



Sign in to add a comment
Intelligent lazy loading of tabs when Chrome launches with lots of tabs
Reported by jeffreyc@google.com, Nov 29 2011 Back to list
Ben/Darin, I think there's an email thread somewhere where this was being discussed.. but I can't find it right now.
 
Comment 1 by sky@chromium.org, Nov 29 2011
We've tried the following:
. Wait for tab to be selected before it's loaded. This turns out to annoy many people as there is a noticeable delay between when a tab is selected and it's content available.
. Only allow n-tabs to load at once. This means slower loading sites effect all tabs.

And we currently progressively throttle loading. That is, the first tab is loaded then we delay 100ms to load the next tab or until the first tab completes loading. If the timer finishes before the first tab, we double the delay restart the timer and load the next tab.
Comment 2 by send2a...@gmail.com, Nov 29 2011
How about a "QuickChrome" shortcut option? Basically it can be a command line switch such as "--quick" (that can be put in shortcut) to open a new Chrome window* with none of the saved or pinned tabs. Just the new tab page only, with a message that says the following:

Tabs in a QuickChrome window will be discarded once the window is closed. Tabs that were saved in a normal Chrome session will not be affected by this, and will be reloaded in the next normal Chrome session.

* Behavior of executing the --quick option must be the same whether Chrome is already running or not (that is, open a new window). But the option will be most useful when it's not running. When Chrome is running, this will just behave as an "Open New Window" option without the QuickChrome-ness or any message about it.
If you're not interested in saving the QuickChrome history/cookies, it's roughly equivalent to --ingognito.

In one of the previous issues that brought me here, it was suggested that there should be an option to load pinned tabs and lazy load non-pinned.  That's the opposite of how I'd want to use it.  Given the wide variety of desired experiences, why not just make multiple options available so that users can find a solution that works the majority of the time?

For pinned tabs:
    [] Lazy Load

() "Reopen the pages that were open last" :
    () Lazy Load All
    () Lazy Load None
    () Lazy Load First / Last / At Most X Tabs

() "Open the following pages" :
    - google.com - Lazy Load? []
    - slashdot.org - Lazy Load? [X]
    - wikipedia.org - Lazy Load? []



Comment 4 by send2a...@gmail.com, Nov 30 2011
Actually in QuickChrome I want to save the history/cookies. Otherwise it's easy to just load Chrome in Incognito mode right from the jump list (or using the command line switch). It will function exactly like how I describe QuickChrome should function, except that it won't save history/cookies.
Comment 5 by jamesd...@gmail.com, Nov 30 2011
I wouldn't like a "QuickChrome" shortcut option.  It wouldn't meet my usage needs at all, since I'd still want all of my old tabs, and I'd want open tabs to be saved for the next session.

If a command-line option is under any serious consideration, how about instead making it be "--lazy" and then Chrome could start, restore all of the previously open tabs, but not load any of them until they're selected.  It'd do what people have been asking for without cluttering the UI (which apparently is a big deal; see  issue 104340 ).

Personally I'd rather see some mechanism added to use lazy-loaded tabs sooner than later.  Sitting around noodling on hypothetical ways to design an intelligent system could take who-knows-how-long and isn't doing users any good today.  It doesn't seem like something that should tie developers' hands for the future either if/when they do figure out a better, automatic system.
Comment 6 by teo...@gmail.com, Dec 29 2011
I agree, something needs to be done rather sooner than later. And if most people are annoyed by having to wait for the unselected tabs to load, than having an option in the settings pane is really ideal for power users, who actually know what they're doing.
Another potential usage case:
(this possibly also involves a separate bug, I apologize if this is in the wrong place)

Some wi-fi hotspots use dns redirection to display a 'sign-on' page, before full access is allowed.

If a laptop user connects to such a hotspot, and opens chrome with saved tabs, every single one of those tabs are redirected to the same sign-on page, and their previous position is effectively lost.

In such a case, intelligent lazy-loading would mean only the initial tab is redirected to the sign-on page, the user could then gain full access to the internet, and clicking on other tabs would then load them properly, instead of having them be redirected.
Actually, it appears my comment is a duplicate of http://code.google.com/p/chromium/issues/detail?id=52489

Intelligent lazy-loading of tabs would help alleviate this situation.
+1 for a toggle option. I don't want it to be auto-magic. Lazy loading would still eat up more of a memory footprint than I need and I don't want flash embeds sneaking up on me...

Being able to override that setting on individual tabs (especially pinned ones) would be nice. And something like greying out unloaded tabs (or some other UI solution) would be great, too.
Comment 10 by reik...@gmail.com, Feb 22 2012
>sky@chromium.org wrote

>If the timer finishes before the first tab, we double the delay restart the timer and load the next tab.

WHOA. Bad idea!! You are DOUBLING the delay restart timer each time?

Now I see why I have so much trouble with my 20 windows, 300 tabs and a 3MBps internet connection. It worked pretty well with a 12Mbps cable modem, but at 3Mbps it just locks up and never comes back.

Notice how (2^300)*100ms is one gargantuan number. It only takes a few bad/slow tabs that refuse to load in their alotted time, and pretty soon we have browser that has so much loading timeout delay that it may not finish loading before we are all dead (or maybe even the age of the universe).

Exponential backoff (that's the technical term, I'm sure you all know about it) is great, up to a point, but please fix this problem. No tab should have a timeout of above 1 second before trying the next one in line.

It makes sense to do a limited amount of exponential backoff, but if any tab takes above 1sec to get a response it should be halted and the next tab should be attempted. After having swept through all tabs, go back to the ones that failed and do them again, maybe with a linear backoff and an upper limit of maybe 2 secs, then on the third sweep permit 3 seconds, up to 10 seconds, when you should give up and report in the tab that it is is "unresponsive".

By the way, is it the exponential backoff mechanism that pops up those status windows that say 

"The following page(s) have become unresponsive. You
can wait for them to become responsive or kill them"

That stuff is just making chrome completely unusable unless I have a very fast internet connection.

Yours for a more robust adaptive algorithm...
Comment 11 by reik...@gmail.com, Feb 22 2012
Can someone point me to the location in the code where the exponential backoff of tab loads is implemented. I sure would like to take a look at what is going on.
Comment 12 by reik...@gmail.com, Feb 22 2012
Another way of looking at it: 

The backing off seems to be in the wrong direction.

One should back off on trying to load bad/slow tabs, rather than backing off on demanding that tabs load in a reasonable time. Good/fast tabs should be prioritized, bad/slow tabs should be made to wait, and not the other way around.
I would like to see "Wait for tab to be selected before it's loaded." to be added in the Options. It can default to "off," so that it doesn't annoy anyone that cares about a delay between when a tab is selected and it's content available. I personally wouldn't care about that, and would like the option to do this when I have a lot of tabs opening from the last time Chrome was open.
i agree with above.
"Wait for tab to be selected before it's loaded." is a pretty good solution. Other tabs aren't fully loaded into memory, and thus if i want to just check something quickly online, without loading all other 30 tabs...

I would like to hear some of the dev's opinions too ;)
Comment 16 by nic...@gmail.com, Mar 5 2012
> like to see "Wait for tab to be selected before it's loaded."

+1.

It would also be great to have a "unload tab" function, with some options like "never", "as soon as inactive", "inactive for [10 minutes/1 hour/8 hours]", etc. It could default to "never", which is what's happening now.

Basically, if you're going to have loading of tabs on demand, like firefox, then for all the same reasons that this is a good idea, the unloading of tabs to free their memory and put them into a frozen state, is a good idea too.

Firefox is working on unload tab ( https://bugzilla.mozilla.org/show_bug.cgi?id=675539 ) and it appears to be something that will become a native/core feature at some point ( http://www.ghacks.net/2011/10/22/dormancy-unload-firefox-tabs-to-free-ram/ ), would be nice if Chromium had both the useful automatic load and unload features too.
That "unload tab" function also sounds wonderful. I'd prefer the "wait for tab to be selected before it's load" function first, but the "unload tab" would be a great addition afterwards.
Please increase the priority of this issue and its duplicates  issue 92790  and  issue 104340 . Please be aware that your reluctance to add an option has delayed the implementation.
I just hit a problem today that I think would be addressed by lazy-loading background tabs. Repro steps:

1) I have 10 tabs open to different pages on my corporate wiki server. 
2) The first tab has a userid/password prompt. 
3) I mis-type my password.
4) Chrome sends 10 login attempts to my wiki server (1 login attempt for the current tab and 9 login attempts for the 9 background tabs)
5) 10 invalid password attempts on the wiki server (using LDAP/AD auth) causes my account to be locked.
6) I now have to reset my password and account and am grumpy for at least 10 minutes. In addition, I have to endure taunting from my co-workers for not using Firefox, which already has lazy-loading tabs.

I realize this problem could be addressed by not having 10 tabs open at step 1, or me not mis-typing my password at step 3, and that would be swell, but I think lazy-loading background tabs would be a more fault-tolerant and elegant solution that would also solve the issues the other folks on this issue have expressed concern about.

If the 9 background tabs lazy-loaded instead of trying to load immediately when I type my userid/password on the first tab, then I'd only have 1 failed login attempt instead of 10.

It would be really nice to fix this. =:)
^^^^ Now that's a much more serious problem that can be solved using lazy loading.

Alas, nobody in the Chrome Dev team wants to listen to actual users. That's what they always say they'll do in the beginning. Until they grow complacent and start wanting to dictate to users what the users *should* have instead of what they really want to have.

(But seriously, shouldn't Chrome be sending a login request on only the current tab? Why is it doing that on all 10 tabs at the same time? Really sounds like bad design to me.)
Comment 21 by marja@chromium.org, Apr 20 2012
Cc: marja@chromium.org
Comment 22 by Deleted ...@, Apr 27 2012
So I had to restart chrome today, and after sitting and waiting for all of my tabs to load for 10 minutes, decided to search google on firefox to see if chrome had this feature (like firefox does).  I read through all of the forums, bug reports, and this entire site... and my chrome tabs have still not finished loading.

To put this simply, with this feature, I would be able to go through my tabs as needed and they would be loaded as needed.  Without this feature, I'm stuck sitting here for 30-45 minutes, waiting for every tab to load before the browser is even usable!  I can't even use the task manager to kill all of the tabs.

I don't see any other option than to implement lazy loading.  There's no smart way of loading the tabs that will work for everyone, and the current method is extremely slow and obtrusive for users with 20+ tabs.  If my tabs take more than 30 minutes to load on a high bandwidth line, I don't even want to know how long it would take with my 3G dongle.

Hey look, I was able to finish this comment (with 3 revisions), and my tabs still haven't finished loading...
Comment 23 Deleted
The only reason I use IE is because it launches instantly. But I don't want to use IE, I want to use chrome, and I want to use it now.

By loading tabs on demand (a non-default option, if you must), we would get numerous additional benefits:

No auto loading/playing flash (I can turn plugs back on)
Vastly saved memory
Saved bandwidth (very important to mobile user)
Some people would not get locked out of AD =:)
Chrome would remain the fastest browser out there - atm, it's like windows itself, after a while it feels slow, you dread restarting it.

I would prefer non-loading of tabs AT ALL to lazy loading. Auto expiring tabs sound too risky, you never know what you might lose. Lazy loading looks like a memory leak, as memory usage creeps up in the background...
Comment 25 Deleted
yeah, i completely agree with comment 24, especially with the instant launch of the program and memory usage. I get 4 gb of ram (of 5 i have installed) wasted for 20-30 tabs when doing research :(

Also, facebook is really eating memory like crazy, but i think it is mostly because of some memory leaks, i don't know really.

I don't wanna use extensions for 'saving' current tabs, or sessions...it's annoying. I want fast launching of Chrome :)
+1 for lazy loading only when tab is selected, and a configure option to turn lazy loading off (perhaps, the default).

The original issue that mentioned this was marked as duplicate of this issue and closed. But this issue seems to talk about automatic lazy loading in the background. That might be useful to reduce CPU and network load, but doesn't reduce the memory consumption on startup.

Lazy loading only when tab is selected reduces all of them (CPU, network and memory loads). It does add a delay while selecting (and hence loading) a tab, but I think that delay is minuscule* and the experience is exactly like opening a new link on a web page.

* minuscule compared to the overall slowdown of the system when tens of tabs are opened at startup.
Comment 28 by rsal...@gmail.com, May 7 2012
I am eagerly awaiting for this feature too!!!!!!
I currently have 85 tabs opened, spread in 7 windows.
When I need to restart chrome or windows it is a PAIN, it takes roughly 1 hour to get to usable state, I can´t stand it anymore!
PLEASE..... does anyone know of a extension to do this while it doesn´t get the appropriate treatment? Thanks!
Comment 29 by avu...@gmail.com, May 8 2012
I hate to add fuel to the fire, this bug is the main reason I use ff right now is due to this bug.
I have changed to ff 5 month ago due to this reason, and Im very happy with the decision. 71 tabs opened and ff open instantly.
Comment 31 by rsal...@gmail.com, May 8 2012
Yes, maybe I´ll give it a try... ff here I go.
Plus I get Tree Style Tabs! (the one addon I missed so much using chrome).
Interesting addon. I will give it a try. Also, in ff you have the handy Tab Groups functionality (also known as Panorama), to help you gruop related tabs.
Comment 33 by Deleted ...@, May 8 2012
+1 I really would like this. Usually have around 20 tabs open.
And don't forget to include the addon "Custom Tab Width" to reduce the min width of the tabs (40 is a good size), so they resembles the Chrome tabs min width.
Comment 35 by Deleted ...@, May 18 2012
I know it isn't a total fix but it seems TabMemFree is a pretty close alternative. It unloads idle tabs, by forwarding them to about:blank, and then restores them when clicked. Using this method, current idle tabs will open about:blank pages on startup, making it pretty complete in comparison to firefoxes. Seeing as I left ff 2 months ago, for the 2nd time in 7 years, I don't plan on going back. https://chrome.google.com/webstore/detail/pdanbocphccpmidkhloklnlfplehiikb
I tried to use WebRequest API to stop inactive tabs from loading in my extension. The trick was to imitate Syncronous Message and check from content script if it's tab is active. It sends from content script formal syncronous XMLHttpRequest to the URL of it's own tab and then catches from background html xmlhttprequests whose url match the url of it's tab(figuring that it's our formal request) then check if that tab is active or inactive and if it's inactive cancel formal request. When content script finds that XMLHttpRequest is canceled it calls window.stop(). The trouble is that WebRequest API slows down some pages, some of them for good, even when there is no line of code exept for the listener.

I tried another approach using local storage. It was goood. Even though each active page has to reload after it's loaded, everything works pretty smoothly. It reloads because the first thing that content script does is window.stop() then it sends asyncronous request to determine if the tab is active and if it is it reloads it writing to local storage not to window.stop() next time. But this approach is blocked by Issue 6429: location.reload() doesn't repost form data, so submitting any form with method=post just won't work. Doh!

I tried approach like in TabMemFree, but tabs that have no icons and no captions are not very usable(Hmm... I wonder how he managed to set an icon to blank.html).

If only there were a way to find directly from content script if the tab it's on is active it would be just a matter of an extension.

P.S. Loading tabs on demand is like a next generation feature, and clicking a tab to load it is just the same as clicking a link. Who ever been annoyed by clicking the links, honestly?
Comment 37 by jcg...@gmail.com, May 27 2012
I don't care about background lazyloads, all I want is the Firefox feature where previously-opened tabs are loaded when they become active rather than all on startup.  I don't have to wait an hour like some of these people describe but several extensions (notably Skype click-to-call and Flash) choke and die and I do have to wait several minutes for the browser to be usable.  I generally have 15-20 tabs to restore.

While the delay of several minutes until usability is bad enough, I also have to try to figure out which tabs are fighting for control of my audio device and click those, wait for them to load, stop the audio..  I guess it gives me something to do while I'm waiting on an unusable browser, but I'd rather just start using the browser than play whack-a-mole very, very slowly.

I switched back to Chrome from FF because I no longer do web development and preferred Chrome's sync to FF's addons, but it's horrible when I have to restart Chrome.  I won't be irritated by a delay when loading pages if I click on inactive tabs after startup.  I expect it, and would much rather deal with waiting a few seconds for the tab to load than waiting forever for the browser to work.  Just give me the option, bury it below several layers of options pages if you want, prompt me with a chain of "Are you really, really, REALLY sure?" dialogs, hide it in chrome://chrome/settings/ somewhere, anything's fine as long as I can eventually get Chrome to hold off on loading inactive tabs on startup.  I'd rather spend half an hour, once, activating the setting than 5-10 minutes playing whack-a-mole every time I have to restart Chrome.
Surely this is a no-brainer - so many on this and another change request ask for a non-default option to be provided that enables lazy loading of tabs. No change for default users, but gives the option for those of us that want this feature to have the behaviour of Firefox. Why *not* implement this?
Why is it so difficult to just add the feature as an *option*? We don't want it to be the default, necessarily, but we DO want to be able to turn this feature on and therefore customize our browsing experience to suit our needs. I often work with large numbers of open tabs (100+) and every time I restart my Chrome browser, I need to open the Chrome Task Manager and kill the processes for every tab in order to get the tabs I care about to load in a reasonable time-frame. I do not want, nor need my background tabs to be loaded automatically when I start my browser, and I would really like this simple feature to be added.

Firefox has it, and as a result, I have switched to Firefox for my primary browser.

If Chrome adds this feature (and especially if Chrome also ends up with tab "unloading" options), I will immediately switch back to using Chrome.

I'm with everyone else here: why *not* implement this feature? You don't have to have it enabled by default.  Feel free to bury it as a command-line option or in an about:config page or something.  I don't care how you do it, just do it, please.

I would do it myself, but I'm only relatively skilled in web development, not platform code.

Or -- maybe expose these functions to extension developers, so we can have a Chrome extension that adds this feature for us.  As I said, I don't care how we get this feature, we just want it soon, and we want to be notified of the change when it happens (mention it in the changelog or something), so we can enable it.

Please?

Please?
Comment 40 Deleted
Comment 41 by rsal...@gmail.com, Jun 12 2012
I did it, and I´m glad I did it!
I´m on firefox again. Now I have 114 tabs, spread in 8 windows, and I restart in about 2 seconds!
My chrome with 60 tabs was using 3,8Gb ram, and my firefox uses 0,6Gb!! (0,8Gb with 114 tabs).
I can ACTUALLY use my machine again! (4Gb total, was aways on swap)
Incredibly happy with it. And I found all addons I need, including the ones to mimic chrome behavior, like hilights of CTRL+F in scrollbar...
Now my chrome sits alone, with no tab at all, and still using 200Mb on fresh start... RIP chrome.
Just curious what addons you're using that mimic chrome behavior, especially for "find" functionality. That's one thing Chrome does way better than Firefox.
Comment 43 Deleted
Comment 44 by rsal...@gmail.com, Jun 13 2012
Yes, I agree, default find in firefox sucks, but it is very good now. That´s the beauty of firefox, it´s api is much more open and complete, you can customize anything.
The addon I used is FindBar Tweek. It moves the find bar to the top, removes close button, hilight all matches by default, show hits counter, and show hilights grid in the scrollbar!!!
(I also use adblock, better gmail, betterprivacy, configuration mania, copy link, ctrl-tab, dictionary tooltip, download statusbar, downthemall!, firetitle, flagfox, flashblock, session manager, instantfox, lastpass, menu editor, mozilla archive format, multiple tab handler, open tab count, restartless restart [yes! now I can], righttoclick, skipscreen, tab scope, text link, tree style tab [yes!! missed so much], try again, and uppity... very happy with the results...)
I generally alternate between 10-40 tabs and a single window. I want this feature so that flash will not load in tabs until I use them.
Comment 46 Deleted
@entertheyoni: I agree that having the lazyloading feature at least as an option (if not the default) would be fantastic. There is, however, a fantastic extension to address your specific need: Flashblock. Find it on the Chrome store. It blocks Flash so you have to click on it to load it, which is a godsend sometimes -- especially for those stupid Flash banner ads.

Come on Chromium team, please add lazyloading tabs, or at least expose the required features for an extension developer to hook into. Please?
Comment 48 by rsal...@gmail.com, Jun 26 2012
Now with 158 tabs opened, and happy.
The lack of this feature is actually the ONLY reason I use Firefox instead of Chrome.
Comment 50 by rsal...@gmail.com, Jun 29 2012
For me, it isn't the only one anymore.
The tabs in a Tree and the 1/3 total memory consumption are the other ones.
Tabs in a tree? Is this an extension or a new feature?
Comment 52 by rsal...@gmail.com, Jun 29 2012
It´s an extension, the one extension I missed the most when I went for chrome.
It´s called Tree Style Tabs, the best single thing after the tabbed browsing itself!
Comment 53 by belic...@gmail.com, Jul 20 2012
This feature is exactly why I'm now using Firefox.
The main reason is, that when searching through web I often open many many tabs for later use. Next time when I start Chrome the loading time is just bad. Somebody can say "Well why are you opening so many tabs?" and my answer? Because I CAN!
Comment 54 by rsal...@gmail.com, Jul 20 2012
home = 480 tabs opened (after a youtube and dailymotion session...)
work = 190 tabs.
It´s good having no limits...
I have to agree, I don't even have a "ton" of tabs on startup.  Usually about 8 pinned tabs on launch, and it still takes a long time to load those.  Also, since the latest Chrome( Tried beta, dev and stock ) it seems, sometimes( maybe 1 out of every 4 ), times I cold start Chrome with any more than 4 tabs, some of the tabs wont even load, just sits there trying to load them, until I click stop and refresh.  Don't know if that's just me or others are seeing it.  But regardless of the reason, this feature would resolve that, as well as slow load times, and memory usage, etc... I don't even care if it's a flag you have to set manually.  If it wasn't for Anrdoid sync'ing I'd probably already have switched to Firefox for this reason.
Comment 56 by Deleted ...@, Aug 8 2012
I too don't understand why this option (well requested) isn't present yet .. :(

For the moment I keep both Firefox and Chrome and switch between them just because of this feature :\

Is it that hard to code a switch ? Cmmon, it's not like we're talking about "a" browser, it's the best browser on the matter.

Thank you,
Dragos
+1 single most important feature!! If we could "+1" these comments you would see how much interest lies in this topic...!!
> If we could "+1" these comments you would see how much interest lies in this topic...!!

That's what starring is for.

Everybody, please restrain further "OMG this is so important, we need this" sort-of comments. These comments dont't help anyone. Just pressing the star left of the bug's title is enough to show that there's a high interest in this bug.

Thank you all!
Comment 59 by rsal...@gmail.com, Aug 8 2012
Interest? In this bug? Not at all, I´ve moved to firefox.
And haaaaaappyyyy... Uninstalled chrome for good.
@rsal That was precisely the type of comment we're not supposed to leave here.

OK, let's get this out of my system: FWIW (coming from a diehard Chrome fan), I'm using Firefox 50% of the time now.

Chrome is lovely for a low number of tabs. This is what most users do, so I suppose it isn't as high of a priority. Sadly, lack of this feature might be costing Chromium some of the people who matter -- the devs. (Offset by the devs gained in proportion to market share...?)
yep, since the chromium devs aren't gonna change anything about this matter, even after many months now, i have switched to using FF and Waterfox (64bit version of Firefox).
I must say, am very happy with it, and i have 130 tabs opened instantly because of the Lazy tab loading feature!

Now for me, as a web developer, it is so much easier to work and do research.
I think the next step for FF is to make an option "Unload tab" ;)
Comment 62 by rsal...@gmail.com, Aug 12 2012
@muntoo No, it is not. It was the "OMG this is so important, we need this" sort-of comments. If you see a little history, will find that I helped a lot in the thread. And was trying to help just a little more, by confirming I am still happy with ff and not missing chrome anymore. Take care.
@rsal I consider 'helping' to be suggesting implementation details/API/etc. Not that I did much either, so I'll shut up now.
No point bitching and whining. This feature was introduced in FF v8, and FF has progressed to v14 now. I thoroughly loved the feature in FF from the very beginning, and I enjoyed how I can have my tabs saved YET load Firefox within mere seconds. What's more awesome is I can have as many tabs of YouTube videos as I want and none would start playing until I activate the tab (No more jumbled noise of gazillion videos playing together). Chrome on the other hand slowly loads each tab, and even plays multiple videos - it's annoying to have to go to each video tab and pause the video.

But as I said, no point bitching and whining here. Their "tests" seem to indicate to them that this isn't a priority despite all the comments here (and there) in favor (I'm sure most of you have even starred the issue). After all, the comment (in  issue 104340 ) "No need for an extra UI option. We should just figure out the best way to do this, and do it automatically." seems to indicate that they think they can slap us with a "one-size-fits-all" solution and we should just take it at face value and STFU. And this is going on while they conveniently forget that Chrome's Settings page has a plethora of UI options that aren't as simple as someone getting a "one-size-fits-all" solution thinks they are. When will they understand that customizability is the key to great software?

Let's all give up and move to Firefox 14+ or really Firefox 8 and anything above. It's sad that Chrome claims to be fast, yet doesn't want to realize it can truly be faster with just a simple option added.
Comment 65 by rsal...@gmail.com, Aug 14 2012
In fact, this option isn´t for keeping youtube videos from playing. We have addons just for that! Even in chrome.
Install "Stop YouTube Autoplay" and even if you was loading all tabs at once, the videos wouldn´t start playing.
For chrome, install "Stop Autoplay for YouTube".

This option is to make a huge saving in memory consumption, and by that don´t slow your machine to a crawl. Also you get super fast restarts. 
Comment 66 by dk.v...@gmail.com, Aug 14 2012
I'm using Magic Actions to make videos not autoplay and a lot of other cool stuff
http://www.chromeactions.com

Along with TabMemFree https://chrome.google.com/webstore/detail/tabmemfree/pdanbocphccpmidkhloklnlfplehiikb

I hate it when people are too lazy to look for solutions and start bitching around here stuff like "omg chrome sucks, going back to firefox". Seriously, stop acting like kids because this thread should be constructive and it seems to be degenerating. Enough!
@rsal - That's wonderful and helpful for the YouTube issue, but it doesn't stop Chrome from slowing to a crawl every time I open it with a saved session numbering in the hundreds of tabs. Sure, by using FlashBlock or some similar extension, and NoScript or something similar, we may save *some* of that loading time on *some* tabs, but plenty of tabs still hang when loading that many at once.

Every time I reopen a saved Chrome session, I find myself going into the Chrome Task Manager and ending the processes for every single tab, plugin, and extension in order to get Chrome's memory usage down to a reasonable size. Then I go through my tabs and load just the ones I intend to use right away by refreshing them. I should not have to do this. A web browser should be intelligent enough to know how to handle itself. You can't brute-force load 200 tabs at once. It just won't work. The network connection won't allow it, and neither will the computer that the browser is running on.

All we're asking for is a simple checkbox in the user settings to enable or disable lazy loading. Either that, or expose the ability to do this very thing in the extensions API, and maybe someone will make an extension that does it. We don't much care how it gets done; we just want it done.

Until then, I will just continue to use Firefox, thus depriving Google of some very valuable information about my browsing habits which it siphons directly from my browser when I'm using Chrome.
Comment 68 by teo...@gmail.com, Aug 14 2012
This isn't really a feature request. It's actually a bug. It's something the programmers did not think of when they designed Chrome. It's funny how Chrome for Android doesn't suffer from the same bug and only loads a tab when you switch to it for the first time, after the initial load of the app.
@dk.vali - I just tried several different tab "parking" extensions. They work...alright, but they aren't what we're looking for here in this thread. They will be an acceptable crutch while we wait for the dev team to take us seriously. One problem I have with it is the lack of the ability to immediately park a tab simply by clicking the button. Unload has a nice option that prevents tab loading when opening new tabs (for those of us who open ten plus links at once when researching) and allows parking on click of the button. Same with Tab Memory Purge on the button-click, plus it has a whitelist that allows you to type in domains you don't want to ever auto-park.

In trying these three tab "parking" extensions out, I'm not sure which one caused it, but my extensions cycled for some reason, and all the "parked" tabs magically vanished. I managed to un-close the last ten tabs to have been closed, but the several hundred other tabs that disappeared are permanently lost. That seems to counteract the desired effect of preserving open tabs without needing to load them. Too bad I didn't have a session manager installed.\

Despite Chrome extensions being available to make attempts at addressing the issue, I'm still sticking with Firefox. At least it offers stability in that regard.
@teo on the contrary, it's a feature request. A bug is when something doesn't work as designed, and since this wasn't part of the design it ain't a bug. The Android version has very different requirements, hence different design.
Comment 71 by teo...@gmail.com, Aug 14 2012
It may not have started out as a bug, but since more and more people are running into the issue, it's becomingeone.
Labels: Restrict-AddIssueComment-Commit
Status: WontFix
There's no real action to be taken with this bug.

We're simply not going to add a bunch of options to let people individually tweak tab-loading behavior, for the same reasons that we don't add fine-grained options to control all other Chrome behaviors.  As for changing the default behavior, comment 1 already notes some behaviors we've tried and rejected.  In particular, we're not going to do Firefox-style lazy tab loading, because when we tested it we were extremely frustrated with it.  This isn't an issue of not thinking of it, or not listening to people suggesting it, not "taking you seriously", etc.  We simply don't agree that the benefits of this are higher than the costs.  One great thing about having multiple browsers is that other vendors can make different design tradeoffs and users can use other browsers when they find something that suits them better.

So in order to move forward here, we need a refinement of our progressive-loading algorithm that does a better job balancing responsiveness, overall startup time, etc.  We're certainly open to such refinements, but they're likely to be lost in the noise on a bug with this many comments.  So for serious, detailed algorithmic proposals of how to improve things, file dedicated bugs.  I suggest reading the code in question first lest you misunderstand what the current code does (a la comment 10 -- we could never reach 2^300*100ms as we trigger new tab loads every time an existing load finishes).
Comment 73 by marja@chromium.org, Oct 15 2012
Cc: sky@chromium.org pkasting@chromium.org
This issue is popping up again, as a possible solution to make flash videos etc *not* play after chrome was forcefully restarted, pls see issue 153199.
Project Member Comment 74 by bugdroid1@chromium.org, Mar 11 2013
Labels: -Area-UI -Feature-Browser Cr-UI-Browser-Core Cr-UI
Blocking: chromium:153544
 Issue 225266  has been merged into this issue.
Cc: pavanv@chromium.org
 Issue 161948  has been merged into this issue.
Incidentally, for anyone still watching this bug, we've made a few rough improvements to our tab restore algorithm and are looking to refine it more.  The ultimate goal is for session restore to be fast, leave the browser usable at all times, and stop loading tabs before the system becomes resource-contended, at which point any remaining tabs will be demand-loaded a la the Firefox option.
Sign in to add a comment