New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 153199 link

Starred by 174 users

Issue metadata

Status: Available
Owner: ----
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug

Blocked on:
issue 446323
issue 509135

issue 804602

  • Only users with EditIssue permission may comment.

Sign in to add a comment

Flash videos etc. on background tabs are started automatically after session restore

Project Member Reported by, Sep 30 2012

Issue description

Version: 23

After doing a session restore, e.g., youtube videos opened in background tabs start playing automatically. It's a real pain, since the user needs to hunt down which tab is causing the noise. At least when I restore my browser session, I often have several tabs with paused youtube videos open in them, and I never *want* them to start playing on the background.

Could we delay the plugins in a click-to-play manner in the background tabs restored by the session restore? Or it could be enough to just select the tab to start playing.

sky, bauerb, wdyt?

Comment 1 by, Sep 30 2012

Oops, forgot to mention, that the e.g. playing videos makes the tab loading slower, and this can be a problem with users who restore a lot of tabs simultaneously.

Comment 2 by, Oct 10 2012

 Issue 154914  has been merged into this issue.

Comment 3 by, Oct 12 2012

Status: Assigned
hey Marja, do you think you could prioritize this for an upcoming milestone? We are getting some user complaints about it, now that we're using Finnur's auto-restart-Chrome-after-2-hours-of-idle-time bubble more aggressively. Apparently it's causing people to wake up in the middle of the night :) (because Chrome auto-restarts and their videos start playing)

Comment 4 by, Oct 12 2012

There was (for the old  issue 3477 ) the idea of using prerendering (which automatically delays loading plug-ins), but I have no idea how to pre-render a tab *instead* of loading it normally. Simply passing a flag through that we can use in ChromeContentRendererClient::CreatePlugin to show a placeholder instead might be easier.

Comment 5 by, Oct 12 2012

I think komoroske@ would be able to point you to the people who know about pre-rendering.
mmenke implemented the deferred plugin instantiation for prerendering, using some of the click-to-play portions. 

Comment 8 by, Oct 12 2012

The plug-in stuff I know about ;-) The question is just whether we go via prerendering, or directly use the same mechanism.

Comment 9 by, Oct 12 2012

Labels: Mstone-25
throwing an Mstone label on; feel free to readjust.
I know at some point we talked about simply deferring Navigation for any non-visible tabs on session restore, for faster startup (less CPU and network contention). If that were done than it seems like it would address this use case as well. 
Instead of actually prerendering the tabs, we could just tell them that they're prerendered.  Tabs are gullible.

Deffering loads could be good, too, but then the use will always have to wait for them to load when he clicks on one.  Suppose we do favor the cache on restore, anyways (At least I think we do...Don't we?)

Comment 12 by, Oct 12 2012

Although I initially liked the idea of deferring Navigation, I've come to dislike this based on how the experience feels in other browsers.  On a fast network, I like the fact that Chrome has all tabs loaded and ready to go quickly, but the experience is a little painful when I am on a slow connection. 

Would it be possible to defer navigation if we start seeing contention in the network ? (I realize this isn't really the point of this bug) 

Comment 13 by, Oct 15 2012

Deferring loads after session restore aka lazy loading was discussed in  issue 105666 , and it was decided we're not going to do it.

One option would be to do the lazy loading only after chrome was forcefully restarted, but not after a normal session restore.

(Although, after a normal session restore, flash videos etc. should still not start automatically imo, even if we load the pages automatically.)

Comment 14 by, Oct 15 2012

Why make the lazy loading a second class functionality, only to be used when chrome will be forcefully restarted?

I would like to see it as an option in the settings as well as used in the event of a forcefully restarted chrome.
Lazy loading doesn't solve this problem anyway, because videos in foreground tabs would still play.  And that would happen in more cases than just "the user was already playing the video so this wouldn't change anything" -- paused or stopped videos would play too.  I suspect without proof that these are actually the majority of the cases in which at least one tab has a video.

The only real fix I could see to the problem on this bug is to disable auto-restart when open tabs have instantiated plugins, which would practically mean that we'd disable auto-restart all the time, unless we also want to switch Chrome to click-to-play mode by default.

This is part of why, now that laforge has said in email that we don't plan to trigger this functionality again in the foreseeable future, I'd prefer to WontFix this bug and file a new bug to remove the auto-restart feature entirely, since it's user-hostile in ways that can't be truly fixed and the costs are higher than the benefits.
>Lazy loading doesn't solve this problem anyway, because videos in foreground tabs would still play

I think it does solve the problem well. The problem in the bug report is that content in the *background* is hard to find with sufficiently many tabs open. If something in the foreground plays then it is easy to stop.

Comment 17 by, Oct 16 2012

pkasting: We could (in theory) make it so, that only the tabs created by session restore are set to "click to play", and if the user creates new tabs, the plugins are not in click-to-play mode, but load normally. No idea how easy this kind of a change would be though.

Comment 18 by Deleted ...@, Nov 11 2012

i also vote for a option: dont load tab until selected
It is not just about the noise from the videos it is about using my bandwidth when I use my notebook and connect through my phone (set as APN) and I just want to send email or something similar and do not wish to get astronomical bill from my mobile operator. 

From a user perspective I would like to be able to disable background things like automatic updates, automatic fetching of data and similar things when I don't need it.
srdjan.mitrovic:  That's a mostly unrelated issue, which would have a completely different solution.  Please file a new bug, so we can keep this one focused on how session restore handles flash and the like.
Thanks for reply, that  issue 105666  was marked as Wont fix.

And it is not completely unrelated because resolving that issue would solve this issue as well.

Users can't comment on that issue anymore so I don't know what is the best way that you can hear users voices? I would like if you could reconsider opening that issue. 
Sorry if I was posting in the wrong place, I will try to find another way but searching for lazy loading in chrome led me here. 
Thank you again.
srdjan:  Not loading/delaying loading tab content is rather different from temporarily disabling automatic updates, sync updates, safebrowsing updates, etc.

Comment 23 by, Nov 20 2012

Common guys, just implement a "Wait for tab to be selected before it's loaded." option? What a simple solution! Or even just a "--load-tabs-when-selected" command line option would be nice.

Comment 24 by, Nov 30 2012

Reading through  issue 105666  shows that NOT implementing intelligent lazy tab loading as in Firefox is simply of political nature...
"As it was decided..." Why not to reconsider and decide otherwise? Too complicated???
I agree with the comment above.

In  issue 105666 , commented:

"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."

I agree with not adding fine grained control for tab-loading behavior but as for the second part, about changing the default behavior... who's "we"? The people commenting on this issue also use Firefox and have actually used both Chrome's "load everything right away" and Firefox's "lazy load tabs". Some of us truly and honestly think that the Firefox way is better!

I don't see what the big deal would be to have a single checkbox (note, not fine grained control) for either doing it the current Chrome way or doing it the Firefox way. Hell, for all I care, this could be a hidden configuration and no checkbox but advanced users could access it in about:flags or whatever! Just make it possible for people who _really, really_ want it to enable it! It can't possibly be a huge thing to implement (if it hasn't been done already)?

Comment 26 by, Jan 7 2013

Labels: -Mstone-25 Mstone-26 MovedFrom-25
Punting non-releaseblocking bugs in M25.  You can find the list via MovedFrom-25
I don't see the problem with adding an option for lazy tab loading. Issues dealing with this ( issue 104340  and  issue 105666 ) have 75 + 189 stars as of now. It seems people really want this optional feature added.

As for now, to prevent YouTube vids loading in the background, there seems to be quite a few extensions for this. I'm currently using
OK, this is one of the most wrong political decisions that can be made. You see a lot of us need to have tabs opened because we need them for our job. Also it is not efficient to save them using an extension and open the session later etc, because sometimes we need to keep as less extensions installed as possible. There's a real need for this feature by the community but Google fails to see it. Lazy loading MUST be implemented and be made available either as an option in settings or as a command line switch. Waiting ages for tabs to open is a real problem. Needing to hunt down for an extension to solve our problem is again a problem because extensions partly solve the problem and sometimes you need to test more than one of them to see which one satisfies most of your needs. In my case I have no big problem at home, but at work currently I am forced to use chrome on a virtual machine with not a lot of memory available. I have to wait 3 minutes initially for usually less than 10 tabs. As for not listening to the community ... In my 20 years of experience I have seen this happening many times. At the end the community always wins. The quicker you realize this the better for the product and its user base. As for me I really like Chrome and that's the reason I am spending a few minutes of my time posting this, however it comes always a time when you have to switch to another product when the current is not meeting your needs. This is how I switched to chrome back in 2008. By that time I was looking for at least a year for a web browser that I wouldn't have to restart every once in a while to be able to reclaim memory, so I installed chrome the day it was released. We are now in 2013 and most of the web pages are way far too heavy. So, it is time for lazy loading tabs. Stop failing to see this. Thanks !

Comment 29 by Deleted ...@, Mar 2 2013

Footab saved me, thank goodness.
Project Member

Comment 30 by, Mar 10 2013

Labels: -Area-Internals -Mstone-26 Cr-Internals M-26
marja: The suggestion in comment 17 is going to be highly confusing to people who have never otherwise seen the C2P UI.  It just looks like YouTube is broken when you switch to that tab.

It seems like a core part of comment 0 is "I don't like having to find the tab playing".  With the new audio indicators for tabs, this ought to be better.  Given that, is there anything else to do here?

Comment 32 by, Mar 30 2013

Dear pkasting,
Are you serious?!  What do you do about multiple videos playing simultaneously?

Lookup  issue 105666 , "Intelligent lazy loading of tabs," which is the sanest and simplest fix to this issue and is ALREADY implemented by Firefox quite successfully.

The highly politicized  issue 105666  also stops unneeded tab reloads on bandwidth-limited connections or insecure connections.

What is this, Washington or Silicon Valley?!  How many senators do we need to do something _this_ obvious.  105666 is considered closed without an  _iota_  of a good explanation, technical or otherwise.

Google keeps flushing Chrome ads into my face.  Well, Chrome's problem is that Firefox has no bugs and the FF team don't act like children!

Comment 33 by, Mar 30 2013

Dear Chromium devs,
Please please please pleaaaaaaase make the world a better place by adding an option to only load tabs when selected.

Comment 34 by, Mar 30 2013

Firefox has plenty of bugs; all sophisticated software does. But the topic at hand, the absence of a lazy-loading option for tabs, is my pet issue and most critical issue with Chrome. I leave about 40 tabs open in Chrome, including a couple of videos, just to remind myself any time I launch it why I can't use it anymore. It's been about a year since I've heard the all-too-familiar sound of five or six YouTube videos suddenly, startlingly, playing over top of each other because I failed to take the time to carefully find each of their tabs and close them before exiting Chrome.

I've been following this thread for awhile, but until now was discouraged from posting by the finality of the WontFix status on  issue 105666 , the subject of which describes precisely what I was hoping for—and waiting patiently for with each Chrome update. I had relegated myself to the idea that Chrome would never be compatible with my browsing method of leaving many research pages or pages of interest open between sessions. It's not uncommon for me to have 300 tabs open in six or seven tab groups in Firefox. 95% of those will lazy-load on start and use very little memory...and no bandwidth. At work on our crappy business Internet this ends up being an issue for me. If I suddenly saturate my connection, our VOIP phones start dropping.

So why not just create bookmarks to all these pages? Because it's a lot of work to manage and organize bookmarks and, simply, because I prefer to have pages immediately at hand in tabs, available with a single click with their spatial position predestined and known.

Consider this my appeal for lazy-loading of tabs, obviously. Consider:

Chrome | Settings
On startup
- Open the New Tab page.
- Continue where I left off.
- Continue where I left off but do not load inactive tabs until I click on them.
- Open a specific page or set of pages. Set pages

Thanks for listening. I hope, pkasting et al., you'll take this as constructive criticism from an avid ex-user and not just further piling on.

Comment 35 by, Mar 30 2013

I too am an ex-user at this point, sadly. :( The only reason I've switched to firefox is because it loads tabs when I want them to. Literally, that's the only reason. I like everything about Chromium (more than Firefox), except that startup experience is horribly annoying to the point I'd rather just use Firefox.

Comment 36 by, Mar 30 2013

Why is this so hard to implement? I have about 50-70 tabs opened, and I always need to mute sound once Chrome starts (as many videos are loading at once), and then go to task manager and manually kill flash plugin and tab processes that take up more memory than I want them (I have a practice to kill anything using more than 100MB there). The traffic used by these background tabs, that I will probably never open during a single session, is huge! Is it so difficult to just load the tab only when actually needed?

I've seen a suggestion to add some kind of indicators for the tabs that have sound. While it is definitely good idea, it won't help me with this problem, as I have more tabs than fit on the screen and I would simply not see the indicators.

In other words, this is the most clean solution to just not start background tabs from previous session until they are clicked: startup time is HUGELY improved, memory usage is HUGELY improved, traffic consumption is HUGELY improved, user experience of not having to scroll through the tabs looking for the one making noise, is also improved... at the cost of a single checkbox.

Comment 37 by, Mar 31 2013

I'm with #34 and #35 on this.

For me, it has nothing to do with youtube tabs, sites that play music, or anything else.  Those might be annoying, but they're ancillary to the issue and most of the time my computer is muted anyway.

For me, it's simply the amount of CPU and RAM that it takes to suddenly load several hundred tabs.  It used to be, whenever I had to relaunch Chrome, my choices were A) wait 5-9 minutes for my computer to become usable again, or B) start killing every chrome.exe process that had 6 threads via the task manager. (The one process with more is the master process, and will shut Chrome entirely if it dies).  

The minute I switched over to Firefox, I stopped fearing restarting my browser.

----------- said on  issue 105666 : "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."  

Well, I'm extremely frustrated with the current behavior, but since it seems that either no one on the chromium team shares my browsing habits, or everyone there who does has a powerful computer with a huge pipe (which I can totally believe), I don't expect to ever go back to Chrome. 

Comment 38 by, Mar 31 2013

By the way, I found a way to make Chrom[e/ium] pseudo behave like Firefox. Simply disable the network connection before starting Chrom[e/ium], then when you start it, all the tabs will throw an "Unable to connect to the Internet" error. Then you can re-enable your network connection, then refresh only the tabs you need, thus preventing every tab from loading at once. An option in Settings sure would be nice though.

Comment 39 by, Mar 31 2013


I can't test your suggestion now, because the latest updates I tried, on my Ubuntu-12.04 box(both Chrome and Chromium) had a KILLER bug that completely crashed my entire Gnome desktop session.  Other people have also complained about such a bug.  It may be fixed by now.

However, there may be 2 problems with your suggestion:
1.)  After clicking a tab, do you still have to click "reload?" (NOT good!)
2.)  What are the tab titles?  "Unable to connect," or the actual web page title?

Such little details are extremely crucial.  My browser isn't just a cool toy to show off to my friends!  It's my life-blood.

The browser HAS TO WORK, snappily and efficiently.  That is Google's whole  _point_  with Chrome.

Larry and Sergey have poured so much into this browser.  It is snappy, clean, and cool at it's core, but because Google believes in democracy, and doesn't do QA-policing of it's programmers, the product suffers, over little details that should never be an issue in the first place.  Ideologies and egotism are dangerous.  They can render a good thing useless;  and that is sad.  

So much talk over a simple checkbox is just wasteful!

Comment 40 by, Mar 31 2013

Yeah, you have to actually press the reload button.
Also, the tab titles show the actual web page titles from last session.

Hey, maybe if we each go make a new bug report about this, they'll give in and add the feature?
Extra bug reports are not useful, and won't make it any more likely the feature will be implemented, unfortunately.

I'm not terribly familiar with the extension APIs, but I'm pretty sure it would be possible to write an extension with the behavior you guys want, if someone has the inclination to do so and some programming knowledge.

In particular, on start (And maybe session restore), you can get the IDs of all relevant tabs, and then use the WebRequest API to block all requests from those tabs until the user focuses them, at which point the tabs can be automatically reloaded if needed.
 Issue 225266  has been merged into this issue.

Comment 44 by, Mar 31 2013

Hi mmenke, that's a good idea.
pkasting: The problem is not only "the user needs to know which tab is making the sound", but the fact we start producing sound after a session restore.

For example, we can't auto-restart Chrome because of security updates, because if we auto-restart, and some tabs start producing sound, it's highly annoying to the user (e.g., in the middle of the night).

We could do it so that by default all tabs created by session restore are muted, and they only start producing sound when the user clicks them.

Note: now that we have per tab sound indicators, this is possible to implement / fix, too.
Personally, I like that Chrome loads all tabs by default, at least after finding and becoming accustomed to a half-way decent tab/session management extension. But at the very least it's worth adding an option to lazy load given that there are many significant issues for users with more constrained systems than a developer's $1000+ laptop running on a high bandwidth network (and for digital hoarders who love to keep 10s or 100s of tabs open).

Adding a lazy load option to about:flags or the command line, if not in advanced settings, seems to address stated reasons for closing related  issue 105666 , and other unstated concerns:
- It does not change default behavior.
- It should appease all sparse UI advocates.
- It should not concern performance advocates because the overhead of a lazy load check should be absolutely miniscule compared to the work required to actually load a webpage.
- When activated, the behavior is on par with opening a link in a new tab.

Feature proliferation can certainly be a scourge, but given that a competitor who has been focusing a lot of late on reducing UI/feature bloat has already made the same tradeoff much more aggressively (not only is there a user visible option, but it's on by default), I suspect  that the very real user need for this capability is not being given sufficient weight here. It could easily be argued that there are sufficient issues for more average users to warrant adding the option to settings (not just about:flags or cmdline), as many fellow posters have tried to express.

Lazy loading solves sound / plugin issues:

- Users frustrated trying to find videos / music in background after restarting.
- Users disturbing colleagues or family members when restarting their browser.
- Users whose desired tabs load slower because of plugins loading/running in background.

Lazy loading solves agonizingly slow / poor user experience issues:

- Users with little system memory, where loading all tabs forces system to use virtual memory, slows down entire machine even after all tab loading is complete.
- Users with slow CPUs where loading all tabs (even one at a time) consumes majority of system resources for a significant period of time.
- Users with bandwidth constraints (slow connection, small data caps, tethering, VPN).
- Users with way too many tabs open.

Lazy loading solves other issues:

- Users starting Chrome when connecting to a hotspot (every tab is redirected to hotspot login page, effectively destroying their session).
- User starts browser with network connection down, has to reload each page manually.

Lazy loading does not solve:

- Users getting woken up in the middle of the night from sound in foreground tab on autorestart.

There are of course many alternative solutions that each solve a more limited set of problems and may have other unwanted effects (many of these solutions fail to solve the same problem that lazy loading fails to solve):

- Click to play / deferred plugin instantiation
- Audio indicators for tabs
- Tabs created by session restore muted
- Don't load more background tabs when network contention is detected
- Don't load more than x tabs in background
- Disable auto-restart
- Disable auto-restore on auto-restart (surface prominent option to restore tabs instead, similar to post-crash behavior)

No matter what solution(s) are chosen for this defect, it seems lazy loading really deserves a second chance.

Comment 47 by, Apr 2 2013

Well said. I also want to point out that some people have been considering "lazy loading" to mean not loading all tabs at once, but maybe one or two at a time, but still in the background and without the user clicking on the tab. 

What we want here is strictly for tabs to load only when they are clicked on. It doesn't have to he by default, but having an option to enable it would be perfect.

A couple of's points are my main reasons for wanting lazy load:

  -- My desired tabs load slower because of plugins loading/running in background tabs.

  -- Loading too many tabs at once makes Chromium fill up my swap space, after having already filled all my memory, leaving my system horribly unresponsive.

  -- My session gets destroyed when I go to Starbucks and launch chromium before remembering to disconnect the network first. I lose all the content I had in those tabs because Chromium thinks every page redirected to the Starbucks login page.

You might like to know that I use my tabs as a sort of food list. I keep tabs open when they relate to a project I'm working on, and having the full history in the open tabs can serve as a refresher to the research we were doing, which beats the extensions made for saving tabs, because those extensions don't have a way to save a tab's browsing history.

For example, I might be reading documentation for an API in one window, and it's nice to have all those tabs open, and then be able to press the back button to go back to the Google search listing that landed me on the page. Saving all the tabs in a favorites folder is not merely enough, as all tab browsing history is lost.

Lazy loading (clicking on tabs to load them) would be a nice solution.
Labels: -M-26 M-28 MovedFrom-M26
Bulk edit: Moving non-release blocking bugs to M28
I have given up on Chrome because I rely on Firefox lazy load feature. I came here because a mailto link in Firefox started Chrome to get me to gmail. I then killed the flash plugin, muted my computer, and turned off my speakers...just to be sure the sound doesn't come back in the middle of the night. So I am here to find a solution to make Chrome usable again.

It surpises me to find this is a controversial problem. I think some research into the demand for lazy load might make a more persuasive argument.

If someone could direct me to any extensions that replace the need for lazy load, I will try them. I have lost many hours of research when Chrome has failed to restore my tabs after a crash. So I could be convinced there are better ways of managing my browser. But so far the session management methods I have tried do not equal the utility of many open tabs.

Someone hinted that an extension is possible. That would be the best way to get rid of this debate.

For now my main browser remains Firefox. Thanks for all the fish.

Comment 50 by, Apr 4 2013

@gearspr(#49) said, "Someone hinted that an extension is possible. That would be the best way to get rid of this debate."

An extension is NOT a good way to resolve this.  Chrome lacks other critical features like the bookmark description field(Firefox) that I'm not complaining about, because an extension _might_ solve that problem in a reasonable manner.

Extensions frequently become dysfunctional with a browser version upgrade because they are unmaintained/incompatible.

ALSO NOTE (regarding browser version upgrades) that Google is a highly innovative and futuristic company whose founders look 20 years into the future(and we love that!)  But, I DO NOT trust Google as a "conservative" software company to maintain compatibility of software/features(like Intel maintains x86 compatibility 30 years after the fact and Microsoft maintains MSDOS compatibility.)  For example, Google Groups no longer honors it's older links, which is really bad.

Extensions fall into 3 categories:
1.)  Extensions with NO state(stored data.)
2.)  Extensions that store data.
3.)  System level extensions that affect "all tabs," system and network resources, and privacy and security issues.

In category (1) 
I have a "word highlight" Firefox extension.  I sorely miss it in Chrome(never found anything like it,) but I know it COULD be easily done.

In category (2)
We have the Firefox "bookmark description field."  This _might_ be reliably implemented by an extension, because extension storage features are based on HTML5 storage/SQL  _standards_, and one would hope that Google DOES honor HTML5 standards, even in the future.

In category (3)
We have the present Firefox "lazy load"/youtube feature.  Needless to say, category (3) stuff should NOT be implemented through extensions, because it must work as soon as the browser loads, and not  _after_  it checks and downloads updated versions of the extensions(assuming they even exist, are maintained, and are compatible!)
I 'only' have 20-30 tabs open, and want the 'lazy load' feature so that I can quickly open the browser to check something if I need to, without having all the system resources taken up by loading unnecessary tabs.

I, too, have turned to IE in recent months for my quick-lookup-needs.

I normally use Chrome and Firefox, one gmail account per browser. I used to use Chrome a lot more, but it was making my system lag and hang so much, that I had to switch most of my reading to FF. I'm still looking for a browser that can handle multiple tabs without lagging so much. (My system is approaching 3.5 years old, but it's got 4GB of RAM, so should perform better, IMO. Time to offload and defrag, I guess.)

In FF, I use Session Manager when I need to save all the tabs--and tab history--and table those for another day, while starting fresh. (Can do per-session or per-window.) I may try installing it on Chrome to see if it works.

I also really dislike the auto-refresh of tabs and would love an option to turn that off.

Comment 52 by, Apr 10 2013, Chromium has never had (I haven't checked in the most recent versions) a feature to let extensions save a tabs history. An extension like Firefox's Session Manager might not be able to restore the browsing history of your tabs in Chrome. 

If Chromium had the ability to save a session including all the browsing history of each tab, that would be a viable solution to the problem at hand. One could save a session (tuck it away) and come back to it later, so that tabs don't load on startup.

However, I still think Lazy Loading is the cleanest solution, and that letting extensions save a tab's history would also come in handy.
I still don't understand what's wrong with loading tabs on demand. Maybe load a few tabs in the background with a <i>lower</i> priority than the currently selected tab. Windows works the same way: foreground stuff gets higher priority than background stuff. But the current tab should have the highest priority.

And, of course, loading 100 tabs into memory is just stupid. Chrome should not use 2GB RAM.

Comment 54 by, Apr 10 2013

@muntoo  you may have missed the subject of this discussion(see above,) which is about Youtube videos(not specifically about tabs.)
Labels: -MovedFrom-25 -MovedFrom-M26 Restrict-AddIssueComment-EditIssue
This bug is getting off-track.  All comments asking for lazy loading are out of scope here.  Closing to external comments.  If you have problems like excessive resource usage, file them separately as requests that we modify the tab load algorithm (which already attempts to only load a limited number of tabs at a time, with lower priority than the foreground tab) to fix the specific cases that are causing you problems (we may need a copy of your profile data to reproduce).  I repeat, the algorithm is supposed to not bog down your machine.  If it does it's a bug and we should fix it.

Incidentally, if you only occasionally need to save your current session and restore it later, consider using ctrl-shift-d (which will save all the open tabs into a single bookmark folder, which you can middle-click to reopen them all later) instead of setting the browser to restore tabs on startup.  This leaves loading the tabs completely under your control.  I realize this doesn't save tab history, so it doesn't suffice for e.g. comment 47.  Allowing extensions access to tab history, if it's not currently possible, seems like a reasonable idea to me.  A bug proposing an extension API for that would be a good idea IMO.  I would be very happy to see "session saver" types of extensions as I think they can be quite useful, albeit for a limited number of people.

In general, extensions are the route we want to promote for most behaviors that we don't think are best for the general userbase, as opposed to options.  Ideally we would support true lazy loading via an extension.  If there are APIs we need in order to do that, then propose them.  And @50, Chrome extension APIs are in general designed to avoid constantly needing the author to rev a "compatible version" number, disabling extensions on start due to incompatibility, etc.  By and large, when we ship an API, we're permanently committing to it.  So extensions ought to be a trustworthy and reliable way to add features.

Finally, I am somewhat curious about comments that make it sound as if restoring all tabs on startup is the only behavior Chrome has, or even the default behavior.  AFAIK, Chrome should NOT restore your tabs on startup unless you explicitly changed it to do so, except possibly for new versions of Mac OS X where I believe by default we obey the system-wide preference that controls this.  The exception was the autorestart behavior that we briefly tested and was quickly disabled (see below).

Now back to the bug at hand.  @45: Correct, we cannot auto-restart Chrome to apply security updates.  We can't ever do this.  It is just flat-out a bad idea that should never happen.  It was a mistake to spend any time experimenting with it in the first place.  There are simply too many pages that have state that results in dataloss on an auto-restart.  Even if you mute video-playing tabs on restart, or in fact even if you don't start the videos at all, the tabs have lost where the user was in the video.

I can't see how this bug is anything but WontFix.  There is nothing to do here.
Project Member

Comment 56 by, May 8 2013

Labels: -M-28 MovedFrom-28 M-29
Moving all non essential bugs to the next Milestone.

Comment 57 by, Jul 24 2013


Comment 58 by, Aug 14 2014

Status: WontFix
This feature would require "tab muted" indicators and per-tab muting and un-muting functionality. (Or at least a feature to mute the whole browser.) The UX team has decided against it (see  ).

So this is WontFix.
Blockedon: chromium:446323 chromium:509135
Status: Started
marja: This idea was ahead of its time, but I think it will happen!

446323, defers all Flash in background tabs, which includes the Session restore case. It doesn't affect foreground tab Flash, so that's still a hole.

509135 stops autoplay in HTML5 Video and Audio in Session restore, background and foreground tab.

Comment 60 by, Aug 28 2015

Labels: -M-29 M-47
Bumping to a modern milestone.
Labels: Hotlist-Recharge
This issue likely requires triage.  The current issue owner maybe inactive (i.e. hasn't fixed an issue in the last 30 days).  Thanks for helping out!

These should be fixed:
- Flash on background tabs
- VIDEO on background tabs

These are still outstanding pending an idle user detector:
- Flash on foreground tabs after session restore
- VIDEO on foreground tabs after session restore
Labels: -Hotlist-Recharge hotlist-recharge
Assuming no objections, I'd like to take this over and bring this home in 2016. We're very-very close. Background tabs are taken care of.

All we need is an idle monitor for the foreground-tab Flash and VIDEO.
 Issue 224182  has been merged into this issue.

Comment 66 by, May 18 2016

This seems... old. Are we still tracking this?
Old but the problem still exists for foreground tabs on sessions restore.

We've solved the most egregious 90% of this problem already though (background tabs).

Again -- if someone wants to take it on other than me, by all means go ahead...
Owner: ----
Status: Available (was: Started)
Marking as Available so someone else can take a stab at it if they have time.
Blocking: 804602

Sign in to add a comment