Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ability to suspend all on browser start #49

Open
webOS101 opened this issue Sep 11, 2013 · 13 comments
Open

Ability to suspend all on browser start #49

webOS101 opened this issue Sep 11, 2013 · 13 comments

Comments

@webOS101
Copy link

I would like to see all the tabs except the focused one suspended when restarting Chrome.

@mamartins
Copy link

+1

@krlmlr
Copy link

krlmlr commented Aug 25, 2014

This seems to work for me when I install the GitHub version.

EDIT: Perhaps only the tabs that were suspended before quitting Chrome, not sure.

@fischeversenker
Copy link

Also very interested in this feature!
After installing the GitHub version chrome now starts with all tabs unsuspended regardless of the tab state before closing chrome. The Chrome Web Store version at least remembered the suspended tabs.

... basically just pushing.

::edit:: just found out that the misbehaviour came from some conflict with the Chrome Web Store version i had installed in the same session. Still the much liked request for the option to have all but the last active tab suspended when opening chrome.

@deanoemcke
Copy link
Collaborator

I am treating this issue as a feature request for being able to specify that ALL tabs are suspended automatically on browser restart regardless of whether they were suspended before closing/crashing. This is an interesting feature that I may look at implementing in the future. However it would require me to store favicons and page titles of every page ever visited in order to be able to suspend on startup without actually loading the page first. And screen capturing would be out of the question.

The extension should already have the feature that will resuspend tabs on restart that were suspended before closing/crashing. If you find this feature is not working please refer to this issue: #37

@deanoemcke
Copy link
Collaborator

Not sure this is really worth doing anymore? Chromes start times seem almost instant now.

@chikamichi
Copy link

It still is a very relevant option. Chrome is not that fast, and many "power-users" have many, many tabs due to Chrome lacking a tabs groups manager.

@deanoemcke deanoemcke changed the title Feature request: Suspend all on browser start Ability to suspend all on browser start Jun 8, 2017
@deanoemcke
Copy link
Collaborator

While suspending all tabs on browser start is not really possible (due to needing to load the tab before it can be suspended), I may investigate the possibility of 'discarding' all tabs on browser start which (if it is possible) would delay loading of the tab until it gains focus.

@deanoemcke
Copy link
Collaborator

As mentioned in issue: #263
the chrome extension footab actually achieves this by blocking tabs from starting. It might be worth checking out the source code: https://sourceforge.net/p/footab/code/ci/master/tree/src/

@deanoemcke
Copy link
Collaborator

In issue #655 @dumblob suggested using Native Lazy Tabs for implementing automatic tab discard on chrome restart.
This extension appears to be discontinued, however it is still available from this chrome extensions archive.

FYI: That extension is based on my code in The Great Discarder ;)

@deanoemcke
Copy link
Collaborator

deanoemcke commented Sep 2, 2018

I did some investigation into tab discarding on chrome start as part of my work on issue: #719.
This is not going to be an option unfortunately, which means that lazy tabs is inherently incompatible with The Great Suspender.

When a tab is discarded it can no longer be communicated with, which means for unsuspended tabs, they will no longer automatically suspend based on a timer, and for suspended tabs, if they are discarded before they can load properly they will be stuck in a 'blockhead' favicon state.

Ideally if you want The Great Suspender to operate properly, tabs will never get discarded, only ever suspended.
To try to ensure this is always the case, there is a setting called 'Instantly suspend when system memory gets very low' which will detect when a tab gets discarded, and undiscard and suspend it instead.

@deanoemcke
Copy link
Collaborator

There are 3 alternatives I can think of for implementing this feature (suspend all tabs on browser restart).

  1. Force all tabs to suspend before chrome shuts down (in which case they'll be suspended when you restart). This is a separate feature request: Feature Request: Suspend all tabs when closing browser #700
  2. Investigate 'blocking' the tab via chrome.webRequest a la Footab (see above)
  3. Attempt to suspend all tabs on startup, even though we may not have any favicon or page title information. This may cause the tabs to show a blockhead icon instead.

@dumblob
Copy link

dumblob commented Sep 2, 2018

I'm raising my hand for either of the options (2) and (3).

I find the option (1) not a good one as e.g. in case of any crash or race condition (e.g. some tabs will close faster due to some hard limits in Chromium or in the operating system) this won't work.

@Chris2011
Copy link

Chris2011 commented Sep 5, 2018

This feature is an option in firefox. You can open firefox with all opened tabs, but only that one, which has the focus is loaded, the rest not. This will be awesome :)

dvalter pushed a commit to dvalter/ff-thegreatsuspender that referenced this issue Dec 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

8 participants