-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Constant page crashes #42315
Comments
I'm experiencing the same issue on Fedora Linux 40 Asahi on my MacBook Air M1. |
Yeah, that's what I thought. Brave devs, its probably something related to the architecture (16k size memory pages) and might be an upstream bug. I may try testing regular chromium. |
From Fedora Asahi matrix room:
Brave devs, I suppose you could temporarily revert https://chromium-review.googlesource.com/c/v8/v8/+/5864909 until the official fix is available (16k page size platform are supposed to be officially supported by chromium, so it should be fixed). *update: the chromium project issue is no longer available for some reason. Its nor open or closed, so it might be deleted or now private. |
Same issue here on my Mac Mini M1 running Fedora Asahi Remix 41. Downgrading to Version 1.71.123 solves the issue for now. |
Sharing this report more broadly internally. If anybody else can contribute Crash IDs, or last working version feedback, that would be greatly appreciated. I'm curious also if Chrome or Chromium is working, whilst Brave is not. Details appreciated! |
This fixed it for me:
the working version is 1.71.123-1 on fedora 41. |
I've been working with folks on Reddit and @hollons has been working with customers too. Here are a few crash IDs that @hollons has collected:
And then here's one from the person I am talking to on Reddit (see https://old.reddit.com/r/brave_browser/comments/1gv2rjh/brave_crashing_constantly_every_minute_or_so/):
These might be different than the reports on Linux - I'm not sure yet |
@life00 huge thanks for sharing that information - I'm talking to folks on the Chromium slack and trying to see if this affects other platforms as well. Issue in the Chromium tracker can be found here: https://issues.chromium.org/issues/378017037 |
I have the same issue on PiOS as well. I am unable to even get a crash report sent. Downgrading to 1.71.123 is a workaround. Updated chromium is working fine: Version 130.0.6723.116 (Official Build) built on Debian GNU/Linux 12 (bookworm) (64-bit) Seems to be in Brave. Another open issue: #42312 |
Can confirm the same observed behavior on both F40 and F41 Asahi with 1.73.91-1. Downgrade to 1.71.123-1, as suggested above, worked for me and I now have a stable primary install. I can reproduce this at will on the Beta and Nightly builds as well. It seems to be essentially the same behavior. Tabs open and work briefly and then err out with a SIGTRAP. Here's an example uploaded Crash ID recently generated on Beta: a11b0c00-bd3e-f40c-0000-000000000000 |
IMPORTANT: Your crash has already been automatically reported to our crash system. Please file this bug only if you can provide more information about it.
Brave Version: 1.73.89 Chromium: 131.0.6778.69
Operating System: Linux 6.11.6-401.asahi.fc40.aarch64+16k
URL (if applicable) where crash occurred:
*
This applies to internal chromium pages too. This report was submitted from a crash of
brave://crashes
page, how ironic. Even while submitting this issue it crashes...Can you reproduce this crash?
It happens always. On a fresh install without any modification. On a stable release version.
What steps will reproduce this crash? (If it's not reproducible, what were you doing just before the crash?)
error: SIGTRAP
There are no additional logs regarding the crash when running brave from console.
This is reproducible on 1.74.5 (beta) and 1.75.18 (nightly). It is not reproducible on 1.71.123 (stable) which is the previous stable release available from official brave rpm repo's. Please let me know if you need me to test some versions.
DO NOT CHANGE BELOW THIS LINE
Crash ID: crash/803e0700-8605-eb0c-0000-000000000000
The text was updated successfully, but these errors were encountered: