4

  • Tabs from a previously active group aren't cleared from memory

  • BugsDesktopDone

Steps to reproduce:

  1. Open Activity Monitor and search for "orion" to see all tabs in memory.
  2. Click on a few tabs in Orion to load them into memory.
  3. Switch to another tab group.
  4. Click on a few tabs in the new group for comparison.
  5. Wait 5 minutes.
  6. Watch in Activity Monitor how the inactive tabs from current group disappear, but the tabs from the previous group stay in memory until you quit Orion. (I tried going back to the original group and waiting for 5 mins to see if they would disappear then, but no.)

Expected behavior:
I would expect all inactive tabs to be purged from all groups always.

Orion, OS version; hardware type:
Version 0.99.123.3-beta (WebKit 615.1.16.1)
MacBook Pro (macOS Big Sur 11.7.4 build 20G1120)

Image/Video:
Not sure it's very helpful to capture a 5+ minute video of Activity Monitor?

  • Vlad replied to this.

    Stakker Switching to another tab group does not unload the previous. You have to close it for that to happen.

        Hmm… I'm not sure what you mean by closing a group. I guess you mean if I have the other group open in another window. But I only have one window, so only one tab group is open at a time. ("Switch Saved Windows in place" setting is on.)

        But… even if I had two windows with two different tab groups open, the inactive tabs from both tab groups should be automatically purged from memory if Low Power Mode is on, right?

        • Vlad replied to this.

          Stakker I mean with one window and multiple tab groups - switching the tab group does not unload the switched tab group. Same is in Safari. Orion has an option to "Close" a saved window which will then unload it.

              Hmm ok… it's a bit of a confusing and abstract concept to close a window that isn't (visually) open in the first place, but OK I can see that there are situations where somebody wants to keep tabs in memory in the background.

              However, when you have Low Power Mode selected, then this doesn't make sense to me. Why would I want to keep tabs from another group in memory if I don't even want them in the currently active group?

              Having Low Power Mode selected means I only want to have the current tab (or the ones active in the last 5 minutes to be precise) alive. I think this is what the user expects. And if the user doesn't go into Activity Monitor to investigate what's going on, there could be many invisible open tabs eating up memory without the user knowing about it. It will just look like Orion isn't doing a very good job.

              The Low Power Mode is main the reason why I'm using Orion. (Pages like YouTube eat up almost half a gig of memory, so tabs in the backgroud can easily eat up several gigabytes.)

              • Vlad replied to this.
                6 days later

                Stakker Low power mode will close them automatically after 5 minutes, like it does for any recently used tab. Again even in low power mode someone may want to switch between the contents of few tabs and keep them in memory, which is why we have a 5 min window. So I think that Low power mode would work exactly as you would expect in this context?

                    Vlad Yes, we agree on how it should work. The problem is that it doesn't :-)

                    I just tested it again to be sure:

                    1. I loaded a few tabs in group 1.
                    2. Then I switched to group 2 and loaded some tabs. ("Switch Saved Windows in place" on, so I only have one window.)
                    3. After 5 minutes, I can see the inactive tabs from group 2 disappearing from Activity Monitor. But all the tabs I opened in group 1 are still there in memory, and they will stay there until I close Orion.
                      2 months later
                      10 months later
                      No one is typing