Devs have asked people to try some flags and provide feedback on whether you notice any changes. Only change one flag at a time.
They want to limit disabling the features to one at a time. So go in, disable the feature, then see if you get logged out as usual. If you do, then enable the flag again and disable the next one. Rinse and repeat until you make it through the list…assuming that none of them seem to resolve the problem.
Currently the flags are only available on Brave Beta or Brave Nightly . So you would have to install those if you don’t have them already. And if you haven’t already tested on Beta or Nightly, would be good to do that with the settings “as is” first.
Chiming in to say its affecting me also with gmail specifically similar to how the others here have described. I get logged out of gmail every 2 or 3 hours even while my browser is active.
this is the first time i’ve ever experienced after using Brave for years
Just adding to the list. I am also getting gmail accounts randomly signed off. It only started happening maybe 1-2 weeks ago? BUT, Youtube still works and stays logged in.
All other websites etc are all working fine.
Nothing else has changed on my system.
Tried the standard clearing all browser data, disabling everything.
Even during the same session with Brave open, after a while all the gmail accounts just get signed off. Almost like the cookies are not persistent.
I’m also having this exact issue. Google logs me out of all accounts approx.. every 4 hours while the tab is being active on the browser.
Youtube doesn’t log me off.
Tried to disable brave://flags/#brave-domain-block-1pes
like the guy above suggested, it didn’t work, now trying with disabling this flag, lets see if it works: brave://flags/#brave-first-party-ephemeral-storage
UPD After 4+ hours: brave://flags/#brave-first-party-ephemeral-storage
the above didn’t work for me, I was logged off again after 4 hours.
And the remaining two flags mentioned by @Saoiray are just not there for me, I don’t know where they are at.
@dl57 you saw my note about it only being available on Beta or Nightly, right? Did you try on those or this was all just on normal version of Brave that you tested? Just wanting to confirm.
I have a regular version I’ve downloaded for my windows 10 pc. Nothing special about it. In fact I’ve started using this browser only yesterday. And it is a strange coincidence that this very version the first I’ve encountered came up with this odd Google issue many people are experiencing
@dl57 the flags are for Beta and Nightly. As I said, it’s good for people to test on those as well. These are the versions being worked on and where fixes would land. That said, so far flags aren’t seeming to matter.
Yeah, it’s all weird. Lots of people are trying different things. This has been getting reported by people on various OS and browser versions for years, but it seems to have a big influx of people reporting it now, especially on Brave.
Problem is no clues have been given on figuring out the issue yet.
Earlier person used a VM to install Brave and that one is not experiencing the issue at all. It’s only happening on their one device
Another person reported it happening on either laptop or desktop but not the other…I forget which was which.
I’m using Windows 11 Pro and not having this problem either.
To my knowledge, devs haven’t been able to replicate this yet.
Means the challenge is trying to figure out if this recent wave is only a Brave issue, if it’s something on Google’s end, if there’s some external factor, or a blend of all of it. Then to kind of narrow down once even that gets figured out.
I have a feeling this is just more Google doing AB testing, the same way many people see/saw the adblock warnings while many others didn’t.
Yeah this keeps happening to me like 1 week ago ı just downloaded brave, and when ı close browser or close pc especially closing browser and reopen browser again logging out of my gmail accounts. This is just annoying me so hard. I hope they can fix it asap.
I’m gong to continue monitoring the behavior BUT after Saoiray added a posting about testing the removal of flags in a nightly release I downloaded and installed version 1.84.61. I did not make any changes to the build, just installed it, copied over my bookmarks and then using my Gmail bookmark I launched Gmail and closed the browser. This morning I launched the nightly release and was pleased to find that Gmail was still live on 1.84.61 but when I went to my existing GA version of Brave which is 1.82.66 I found that I was logged out of Gmail. I will continue to see of this nightly release is still keeping Gmail Live while using GA 1.82.66 for my regular activities. The one thing I will do with 1.84.61 is do a side by side comparison of settings as, like I said, I only copied over my bookmarks from 1.82.66. Stay tuned.
People with the problem, please keep brave://flags/#enable-bound-session-credentials enabled and on logout event please open brave://histograms/Signin.BoundSessionCredentials and dump everything you got on this page here. I’m mostly curious if anyone of you got Signin.BoundSessionCredentials.SessionTerminationTrigger histogram and what the value it has in this case.
The flag they mentioned is one that person said they disabled and the issue went away. But let’s not mess with that flag. The focus here is the Histogram for those of you being logged out.
I’d ask that you provide the Histogram data as a reply on the Github if possible. If you can’t or don’t want to do it there, advise and we can look at another way…maybe even just sharing here. Keep in mind you check the histogram thing right after you have a logout issue.
this is what mine looks like, is this enough info? if not, what else is needed to share without compromising my data/info since im sharing this publicly thanks
Histogram: Signin.BoundSessionCredentials.SessionCountOnInit recorded 1 samples, mean = 2.0 (flags = 0x41) [#]
0 …
2 -O (1 = 100.0%) {0.0%}
3 …
Histogram: Signin.BoundSessionCredentials.SessionTerminationTrigger recorded 2 samples, mean = 1.0 (flags = 0x41) [#]
0 O (0 = 0.0%)
1 --O (2 = 100.0%) {0.0%}
2 …
Histogram: Signin.BoundSessionCredentials.StorageReadError recorded 2 samples, mean = 0.0 (flags = 0x41) [#]
0 --O (2 = 100.0%)
1 …
And in that person’s list, you can see it shows Signin.BoundSessionCredentials.SessionTerminationTrigger in the list, which is what the dev was looking for.
I advise to paste the result on https://pastebin.com/ to avoid pasting the whole mess on GitHub. Click on Create new paste at the bottom—no need to have a login
Copy the URL pastebin has given you, and maybe a copy of the value of Signin.BoundSessionCredentials.SessionTerminationTrigger (the one they’re mostly interested in) here: https://github.com/brave/brave-browser/issues/44789
There’s no sensitive data, @blitzio, don’t worry. It’s plain text and not very long, so you can easily verify that in a few seconds.
Check my other answer above to see how to post the information.
If you don’t have a GitHub login, you can put that here, and I’ll try to keep an eye out for that and post it myself on GitHub.
At worst, if you’re still wary about giving the information, give only the last item of my list, which is apparently the most interesting to them. It looks like this:
Histogram: Signin.BoundSessionCredentials.SessionTerminationTrigger recorded 2 samples, mean = 1.0 (flags = 0x41) [#]
0 O (0 = 0.0%)
1 --O (2 = 100.0%) {0.0%}
2 …
Well, I spoke too soon but I’ve uninstalled that nightly install and I’m going to try again as before I made setup changes it seem that Gmail remained live overnight but after changing the settings to somewhat match my GA version of Brave, I was logged out.
