You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When you launch Ungoogled Chromium, a bunch of tabs are loaded automatically in the background, which causes performance issues. Only the currently active/selected tab should be loaded and the rest should be hibernated.
Who's implementing?
I'm willing to implement this feature myself
The problem
When you launch Ungoogled Chromium, a bunch of tabs are loaded automatically in the background, which causes performance issues. Only the currently active/selected tab should be loaded and the rest should be hibernated.
I have preloading disabled. But it still loads the tabs automatically in background. Vivaldi for example does this quite well, where it only loads one tab and that's it. Same thing in Firefox
Possible solutions
Copy the behaviour of Vivaldi or Firefox
Alternatives
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
Same issue for me! It used to work fine until about 6-9 months ago I think. I've been using Slimjet mostly (chromium-based browser) and this is ruining it for me.
Description
When you launch Ungoogled Chromium, a bunch of tabs are loaded automatically in the background, which causes performance issues. Only the currently active/selected tab should be loaded and the rest should be hibernated.
Who's implementing?
The problem
When you launch Ungoogled Chromium, a bunch of tabs are loaded automatically in the background, which causes performance issues. Only the currently active/selected tab should be loaded and the rest should be hibernated.
I have preloading disabled. But it still loads the tabs automatically in background. Vivaldi for example does this quite well, where it only loads one tab and that's it. Same thing in Firefox
Possible solutions
Copy the behaviour of Vivaldi or Firefox
Alternatives
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: