This repository has been archived by the owner on Dec 11, 2019. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 975
Added tab discarding (put tabs to sleep if not in use) #2388
Comments
Thanks for your work on this! 😄 May I ask if this functions the same way as Chrome, and if there is a way to view a Brave equivalent of chrome://discards ? |
@DivineOmega pls post for chrome://discards if you don't mind in a new issue. |
luixxiul
added
the
needs-info
Another team member needs information from the PR/issue opener.
label
Apr 17, 2017
Is there any specific thing to test? |
@DivineOmega it uses the same memory-based tab discarding that Chrome does. We will be adding more features soon. @luixxiul there is a dev menu item that simulates a memory pressure event, but keep in mind that it will only discard non-active tabs and only if they are at least 10 min old.
|
luixxiul
added
QA/test-plan-specified
and removed
needs-info
Another team member needs information from the PR/issue opener.
labels
Apr 17, 2017
Cannot reproduce with RC builds. I attempted to use memory_pressure in bash, but to no avail. |
I don't think that's a reliable way to test. I have tested in dev builds using the dev menu item and it worked correctly.
… On Apr 17, 2017, at 11:44 AM, Alex Wykoff ***@***.***> wrote:
Cannot reproduce with RC builds.
I attempted to use memory_pressure in bash, but to no avail.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or mute the thread.
|
This was referenced Apr 21, 2017
102 tasks
This was referenced Apr 25, 2017
alexwykoff
changed the title
Tab discarding
Added tab discarding (put tabs to sleep if not in use)
Apr 26, 2017
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Test plan
#2388 (comment)
Google Chrome/Chromium currently supports a feature called tab discarding.
Does Brave currently support similar functionality, or if not are their plans to do so?
#1796
The text was updated successfully, but these errors were encountered: