-
-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
Brave and Chromium unresponsive : possibly graphical issue #63968
Comments
Have you tried with Linux 5? |
No I hadn't even noticed that my kernel was so outdated until you pointed this out. |
I have the same problem...
Unfortunately I also have no idea how to debug this It not only happens with chromium but also chromium-based apps like spotify |
@alexameen just FYI: https://unix.stackexchange.com/questions/524205/help-chromium-display-frozen-but-the-app-keeps-working I have not yet tried anything but that seems to relate to the problems we are experiencing |
@alexameen can you try if running chromium with |
Thank you for your contributions. This has been automatically marked as stale because it has had no activity for 180 days. If this is still important to you, we ask that you leave a comment below. Your comment can be as simple as "still important to me". This lets people see that at least one person still cares about this. Someone will have to do this at most twice a year if there is no other activity. Here are suggestions that might help resolve this more quickly:
|
I am having the same issue on Void Linux. Brave just stops responding. It works fine until
|
I marked this as stale due to inactivity. → More info |
Issue description
Both Brave and Chromium browsers will randomly become unresponsive for me. I suspect that it is a graphical failure because I get that classic "burn" effect when any other windows overlap it and are moved (OG windows users might know what I'm talking about here). I know that Brave and Chromium share large sections of a code-base so I'm unsurprised that the issue effects both.
Steps to reproduce
Technical details
The text was updated successfully, but these errors were encountered: