-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Crash in brave!AccountTrackerService::Initialize
(Linux only)
#6192
Comments
I wonder whether tha'ts the crash behind #6054 |
@fmarier this has been a problem for a super long time - seems to have been present since at least Chromium 73 (from crash reports) I'm not quite sure what the impact is to users - is this a renderer crash? From the call stack, it seems to be a hard browser process crash... but I've never ran into it 🤷♂ |
I ran into it twice this morning:
but I didn't really notice anything. |
And some more:
It seems to happen constantly but without being noticeable by the user. I'll restart my browser in a terminal to see if this correlates with console output too. |
This is extremely frequent, no wonder we're getting flooded with these reports:
Reproduction steps on my laptop are simply: leave the browser open for a few minutes. There doesn't appear to be anything in the terminal other than the flood of sqlite errors from #6269 . |
Same here. This is quite strange since the browser actually continues to work... Can't even guess which process is crashing. |
No traces of this since C80 |
Description
Going through crash reports, I'm seeing a LOT of these on Linux. Thousands.
Unclear what the impact is to users
A few examples here:
https://stats.brave.com/dashboard#crash/5d8cbd539557ce001f93a373
https://stats.brave.com/dashboard#crash/5d8cbcf6ed6e87001fe15623
https://stats.brave.com/dashboard#crash/5d8cbce5f686a0001f52aa67
https://stats.brave.com/dashboard#crash/5d8cbbf79557ce001f939cd5
https://stats.brave.com/dashboard#crash/5d8cbb3911ca47001f18d670
Call stack looks like this:
Steps to Reproduce
?
Brave version (brave://version info)
Not a new issue; I saw some clients still on Chromium 73 versions of Brave running into this.
The text was updated successfully, but these errors were encountered: