@Chipp Iām a bit confused on your situation. If you look at your screenshot, you have memory saver enabled but you also set YouTube as an exception. You told the browser not to use memory saver for YouTube and WhatsApp, meaning they will stay active.
It very explicitly says it in the portion there, Sites you add will always stay active and memory won't be freed up from them. Iāll screenshot that portion of your screenshot below:
but what memory saver does, based on the description, is frees memory from inactive tabs, thus what the exceptions list does is not frees memory from the listed websites
at least, thatās whatās the descriptions saidā¦
Iāve seen YouTube reload itself on a variety of browsers when you return to its tab. Doesnāt YouTube normally do this itself after a pre-determined time when āparkedā on the home screen?
(Going on the fact it was parked as you didnāt say a video was playing, because if a video was playing then this is something else as yes it shouldnāt reload at all in that case, memory saver or not honestly since itād be an active tab.)
@Chipp ah, I think I might have been reading wrong a bit earlier. Youāre trying to keep things completely active and youāre saying that it eventually is getting suspended anyway.
Is this just while youāre in Brave and in other tabs or is this after switching to other apps? And is it happening while videos are playing or is it while you have content on YouTube paused?
Not that I can see sadly. However, I have yet to actually repeat this.
Out of curiosity, since it does seem if I artifically limit my RAM, Memory Saver then DOES start refreshing pages it shouldnāt be refreshing, how much RAM does your PC have? I have 32GB of RAM, and Brave usually doesnāt need the memory saver (except YouTube which if left open all day somehow creeps up to 9GB of tab usage, when it started at half a gig in the morning).
I wonder if the system is simply running out of RAM and being forced to unload tabs.
@Chipp sorry I went AWOL on you Chipp. Not quite sure what to say as Iām not really experiencing the issue. The only thing I see is if it had automatically gone to other videos, then it will reload based on whatever video itās now at, as it would have kept navigating.
I cannot keep track of everyone. I am not a machine.
Looking back at your thread you now reminded me of, you were then too told that 8GB is not enough. This explains this as well. Besides, I did tell you in the other thread when I looked that it can only go so far. You have a lot of extensions, youāre trying to use multimedia heavy websites, all on a machine which is not going to have enough.
Iām sorry, but Iām moving on now. (Perhaps next time, be more kindful.)
āIām doing my best to avoid using Whatsapp Web desktop app because it consumes too much RAM when having it open along side Brave (I open a lot of tabs) and other apps (I only have 8GB RAM) so Itās better for me to have Whatsapp Web pinned as a tab web page than an standalone appā¦ā
āCan you try clearing the cookies and cache, then relogin?ā
Re clearing cookies and cache: In a Brave Browser New Window, go to: brave://settings/clearBrowserData and for Time range > All time, using Basic tab:
Enable Cookies and other site data
Enable Cached images and files
Click the Delete data button
Exit / Quit everything
Restart the computer
PS. Your computer apparently has limited resources for the workload of:
Signed in to Google Eco-System > YouTube
Signed in to WhatsApp
ā¦ when using Brave Browser.
In addition, you are dealing with the Google Unified-Login Eco-System that requires persistance of your online identity ā from the Google point of view; and that means, lowering Brave Shields and allowing third-party cookies for the Google Eco-System. You might visit:
brave://settings/content/braveShields (Shields Down section)
brave://settings/cookies (Sites allowed to use third-party cookies section)
And add, one-at-a-time:
accounts.google.com
accounts.gstatic.com
ajax.googleapis.com
api.recaptcha.net
gmail.com
google.com
mail.google.com
myaccount.google.com
oauth2.googleapis.com
recaptcha.net
workspace.google.com
www.google.com
www.googleapis.com
(You might also search online, to find the WhatsApp domain names and hostnames that are essential for its access to persist.)
Because a lapse or misstep in maintaining persistance, might lead to a webpage reload.
To keep WhatsApp Web working smoothly in Brave Browser, you need to allow certain domains/hostnames so cookies, JavaScript, WebSockets, and storage arenāt blocked by Shields.
Hereās a practical breakdown (based on how WhatsApp Web is structured):
Core domains (must be fully allowed)
These are essentialāif blocked, WhatsApp Web wonāt load or function:
web.whatsapp.com
*.whatsapp.com
*.whatsapp.net
In Brave:
Allow Cookies
Allow JavaScript
Allow Storage (local/session)
Allow WebSockets
Facebook / Meta infrastructure (required)
WhatsApp relies on Metaās backend:
*.facebook.com
*.fbcdn.net
*.fbsbx.com
Needed for:
Authentication
Media delivery
Some API calls
Media & CDN domains (important for images, voice notes, files)
mmg.whatsapp.net
pps.whatsapp.net
static.whatsapp.net
If these are blocked:
Images wonāt load
Voice notes fail
File downloads break
WebSocket & real-time messaging endpoints
WhatsApp Web uses persistent connections:
wss://web.whatsapp.com
wss://*.whatsapp.net
If blocked:
Messages wonāt send/receive in real time
Storage-related permissions (critical in Brave)
Brave Shields can silently break WhatsApp if these are blocked:
Make sure to Allow:
Cookies (including cross-site)
Local Storage
IndexedDB
Service Workers
Brave Shields settings (recommended)
For web.whatsapp.com, set:
Shields: Down (easiest), OR:
Trackers & ads: Allow (or standard)
Cookies: Allow all cookies
Fingerprinting: Standard (strict can break things)
Block scripts: Disabled
Common breakage causes
If WhatsApp Web isnāt working, itās usually because:
Core domains (must be fully allowed)
In Brave:
Facebook / Meta infrastructure (required)
Media & CDN domains (important for images, voice notes, files)
WebSocket & real-time messaging endpoints
Storage-related permissions (critical in Brave)
Brave Shields settings (recommended)
Common breakage causes
Quick whitelist summary
Pro tip