Skip to content
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

Open
life00 opened this issue Nov 15, 2024 · 10 comments
Open

Constant page crashes #42315

life00 opened this issue Nov 15, 2024 · 10 comments
Labels
Chromium/reported upstream Issue has been reported upstream and crbug link is in the issue crash OS/Desktop priority/P2 A bad problem. We might uplift this to the next planned release.

Comments

@life00
Copy link

life00 commented Nov 15, 2024

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?)

  1. open absolutely any page
  2. wait 30-90 seconds
  3. the page crashes with 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

@github-actions github-actions bot added the crash label Nov 15, 2024
@rebron rebron added OS/Desktop priority/P2 A bad problem. We might uplift this to the next planned release. labels Nov 15, 2024
@rebron rebron added this to Crashes Nov 15, 2024
@github-project-automation github-project-automation bot moved this to To do in Crashes Nov 15, 2024
@enginqt
Copy link

enginqt commented Nov 17, 2024

I'm experiencing the same issue on Fedora Linux 40 Asahi on my MacBook Air M1.

@life00
Copy link
Author

life00 commented Nov 17, 2024

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.

@life00
Copy link
Author

life00 commented Nov 17, 2024

From Fedora Asahi matrix room:

[@refi64:linuxcafe.chat]
hello, a quick PSA for the chromium users here: chromium 131 seems to have an issue where browser processes crash randomly, because, surprise surprise, V8 actually has a hardcoded 4KiB guard page size, and a recent change makes that size much more load-bearing. fix for me was to revert https://chromium-review.googlesource.com/c/v8/v8/+/5864909 for now. I filed https://issues.chromium.org/issues/378017037 with the details, might try to see if I can fix it later (but probably won't get to tbh).

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.

@NettoHikari
Copy link

Same issue here on my Mac Mini M1 running Fedora Asahi Remix 41.

Downgrading to Version 1.71.123 solves the issue for now.

@jonathansampson
Copy link
Contributor

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!

@kindlychung
Copy link

This fixed it for me:

sudo dnf downgrade brave-browser
Updating and loading repositories:
Repositories loaded.
Package                                                               Arch             Version                                                               Repository                                 Size
Downgrading:
 brave-browser                                                        aarch64          1.71.123-1                                                            brave-browser                         363.6 MiB
   replacing brave-browser                                            aarch64          1.73.89-1                                                             brave-browser                         367.4 MiB

the working version is 1.71.123-1 on fedora 41.

@bsclifton
Copy link
Member

bsclifton commented Nov 22, 2024

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:

Uploaded crash report ID:	65f81400-8605-eb0c-0000-000000000000
Uploaded crash report ID:	62f81400-8605-eb0c-0000-000000000000
Uploaded crash report ID:	60f81400-8605-eb0c-0000-000000000000
Uploaded crash report ID:	5cf81400-8605-eb0c-0000-000000000000

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/):

Uploaded Crash Report ID:	29c71700-8605-eb0c-0000-000000000000

These might be different than the reports on Linux - I'm not sure yet

@bsclifton
Copy link
Member

@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

@bsclifton bsclifton added the Chromium/reported upstream Issue has been reported upstream and crbug link is in the issue label Nov 22, 2024
@p0p-x
Copy link

p0p-x commented Nov 23, 2024

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

@imcleod
Copy link

imcleod commented Nov 23, 2024

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!

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Chromium/reported upstream Issue has been reported upstream and crbug link is in the issue crash OS/Desktop priority/P2 A bad problem. We might uplift this to the next planned release.
Projects
Status: To do
Development

No branches or pull requests

9 participants