Brave (Tab) Crashes Daily

Description of the issue: Brave tabs seem to crash occasionally
How can this issue be reproduced?

  1. Visit youtube

  2. Play video

  3. Crashes (ocasionally)

Expected result: No crash

Brave Version( check About Brave):

Brave 1.91.172 (Official Build) (64-bit)

Chromium: 149.0.7827.115

Additional Information:

Crash IDs (not all were youtube if i remember correctly)

64662900-9a02-c40f-0000-000000000000

62662900-9a02-c40f-0000-000000000000

61662900-9a02-c40f-0000-000000000000

If the crashes are mostly on YouTube, I would first test with Shields/extensions out of the picture: open a private window with extensions disabled, or temporarily turn off the video/download/password extensions and try the same video. Also check Settings > System > Use graphics acceleration; switch it off, restart Brave, and test again. If it stops, the useful extra info for Brave staff is your OS/GPU and the brave://gpu status, together with those crash IDs.

Ok, i am disabling acceleration.

Reproducing it is not that easy, if it happens once or twice per day. Does not matter if its the same video.

And it appears i cannot upload the gpu report file because i am a new user, so i will just add this from Speccy:

NVIDIA GeForce RTX 4070 Laptop GPU
Manufacturer NVIDIA
Model GeForce RTX 4070 Laptop GPU
Device ID 10DE-2820
Revision A2
Subvendor Unknown (1D05)
Current Performance Level Level 0
Current GPU Clock 210 MHz
Current Memory Clock 405 MHz
Current Shader Clock 405 MHz
Voltage 0.620 V
Technology 4 nm
Bus Interface PCI Express x8
Temperature 54 °C
Driver version 32.0.15.9649
BIOS Version 95.06.35.00.0f
Physical Memory 4091 MB
Virtual Memory 4092 MB

Non youtube crash:

01552a00-9a02-c40f-0000-000000000000

If it still crashes with acceleration off, I’d add the crash IDs as plain text like you did and not worry about the full GPU report file for now. One useful split test is a fresh Brave profile or Guest window with Sync off for a day; if that also crashes, it points more to GPU/Chromium/driver side than to the current profile or extensions. If only the normal profile crashes, then it’s worth checking extensions and synced settings one by one.

@Mattches

OP (BlueZero) has Crash ID numbers

Brave (Tab) Crashes Daily
Brave (Tab) Crashes Daily - #4 by BlueZero

@nubeovejita27 My profile is fresh, started on Friday.

Sync settings are already off, they were never setup.

New crashes:

Linkedin:

c6f22a00-9a02-c40f-0000-000000000000

Stackoverflow:

21f72a00-9a02-c40f-0000-000000000000

What is common about these crashes is, the it starts right when the page is loaded. I can see the page for brief moment (<1s) and then i see the STATUS_ACCESS_VIOLATION error. Then after accessing the page again all works fine.

Since the profile is already fresh and Sync was never enabled, I’d probably focus on things outside the profile now. One simple test is launching Brave once with GPU disabled from the shortcut/Run box, for example brave.exe --disable-gpu, and then trying the same LinkedIn/StackOverflow pages. If STATUS_ACCESS_VIOLATION still happens even that way, the crash IDs are probably the most useful thing for staff. If it stops, then the NVIDIA driver / graphics path becomes the main suspect.

I’ve opened the following issue on our Github concerning your crashes for our developers to review:

Another crash ID, this time with “–disable-gpu”

da1d2d00-9a02-c40f-0000-000000000000

And this one is almost reproduceable, but in a private access page to which i cannot give acccess, But is 100% related to Javascript, the page loaded and then Datatables.js was trying to process the data (about 3MB):

167b2e00-9a02-c40f-0000-000000000000

Just before i get that question. I did a check of my memory and its fine.