Startup = hibernation?



  • Hi all,

    I was wondering what is the state of a background tab on startup.

    On startup, Vivaldi loads tabs from the last session (if that's your setting). Are the tabs in hibernation?

    If not, why not?

    I see that the icons of all tabs are in their original colors, indicating they aren't in hibernation. They dim when hibernating (I set that option). When I right-click on one of the tabs, I see the "Hibernate Background Tabs" item, which indicates the tabs aren't in hibernation.

    So, the tabs don't seem to be in hibernation. But they aren't active, either. For example, youtube videos don't start until you click on the tabs.

    I'd like to know the difference between this initial state and the hibernating state. If they are essentially the same, I don't have to do "Hibernate Background Tabs" each time I launch Vivaldi to minimize resource use.



  • Settings/Startup/Startup with/Lazy load restored tabs
    That setting, if set, causes tabs to be reactivated only if selected.



  • @ian-coog said in Startup = hibernation?:

    Settings/Startup/Startup with/Lazy load restored tabs
    That setting, if set, causes tabs to be reactivated only if selected.

    Thanks for the clarification! but that doesn't answer my question. To use that terminology, my question is

    Is the lazily loaded restored tabs in hibernation?
    

    What's the difference between lazy loading and hibernation?

    If they are different, do you need to hibernate the lazily loaded tabs to save resources?


  • Moderator

    @ryofurue Lazy load means the tabs load in the background with a low priority. Hibernate means that as long as they are not focused, the tabs only use some RAM to store current state.



  • @ayespy said in Startup = hibernation?:

    @ryofurue Lazy load means the tabs load in the background with a low priority. Hibernate means that as long as they are not focused, the tabs only use some RAM to store current state.

    Thank you for the information! That means that it's worth hibernating the tabs right after Vivaldi is launched, right?

    And, I suppose that a request that tabs be automatically hibernated at launch is already in, right?


  • Moderator

    @ryofurue Yes.



  • I feel like there is a lot of misinformation in this thread (unless I am incorrect, of course). When you startup Vivaldi and it restores your session, the only tabs that should be loaded are the active tabs in each window (and pinned tabs if you have that setting enabled.) Startup utilizes hibernation.

    Lazy load in Vivaldi parlance means...do not load inactive tabs at all until selected and create no renderer processes until then. Lazy Load harnesses Hibernation to make itself work. Firefox uses the same definition, but Opera on the other hand does what @Ayespy mentions and loads all tabs on startup when Lazy Load is enabled, just at a slower pace.

    On Vivaldi startup, for me, each tab that is not the active tab is dimmed out and when you go to chrome://discards to see the hibernation status, you will see [Discarded] next to each inactive tab. The Vivaldi Lazy Load feature forces tabs to startup as Hibernated/Discarded and reflect this in the UI.

    Unfortunately, this is not always the case though. The above behavior only happens in the UI if both "Lazy Load Restored Tabs" and "Always Load Pinned Tabs" are checked/enabled in Preferences. If "Lazy Load Restored Tabs" is checked and enabled, but "Always Load Pinned Tabs" is disabled, the feature won't work right. At this time, during the startup process, each and every tab will be un-dimmed. Additionally, if you go to chrome://discards in the browser, no tab will show as discarded. However, the Lazy Load functionality is preserved nonetheless. Inactive tabs are still hibernated because they do not have renderer processes, and thus resources, associated with them. You can run right click on a tab and select "Hibernate Background Tabs" or discard them from chrome://discards, but all that will do is update the UI to show a dimmed icon. It's not freeing up resources because there is nothing to free up. (I've put in a bug report on Saturday about this UI inconsistency.)

    Also, I'm not sure why there would be a feature request in for automatic hibernation at launch, because we've already had it for as long as I can remember. (I do know that there is a feature request for automatic tab hibernation after a certain period of time, however, to mimic The Great Discarder's functionality.)



  • Thank you for the information!

    @shrinra said in Startup = hibernation?:

    When you startup Vivaldi and it restores your session, the only tabs that should be loaded are the active tabs in each window (and pinned tabs if you have that setting enabled.) Startup utilizes hibernation.
    Lazy load in Vivaldi parlance means...do not load inactive tabs at all until selected and create no renderer processes until then.

    The startup you describe is clear and easy to understand. But,

    1. What is hibernation, then? Does one renderer process still correspond to a hibernated tab? Is the process sleeping (in the Unix parlance) during hibernation? Or is it killed when the corresponding tab is hibernated?

    2. I set the option to fade the tab icon color when the tab is hibernated. (I also set "Lazy Load Restored Tabs" and "Always Load Pinned Tabs".) Then, I suppose the icons should be faded when Vivaldi is launched. But they aren't. Is this a kind of bug?

    I hope these things are clarified. I wish the tabs were marked "hibernated" when Vivaldi is launched (whatever the internal implementation of hibernation is).


Log in to reply
 

Looks like your connection to Vivaldi Forum was lost, please wait while we try to reconnect.