Brave always crashes with Aw, Snap! (possible conflict with Symantec)

kobelobster commented 5 years ago

I found https://github.com/brave/brave-browser/issues/3288 but the issue is closed

Description

Whenever I launch brave, I'm getting the "Aw, snap" page indicating an error. I can't access the settings or crash reports or anything. Every page crashes. Not even clicking "about brave" opens anything.

Steps to Reproduce

Don't know if you can reproduce this but for me it crashes on every launch

Actual result:

Expected result:

Brave works

Reproduces how often:

Every time

Brave version (brave://version info)

Can't access the page, but according to win software it's 78.0.70.121

Version/Channel Information:

Can you reproduce this issue with the current release? Yes
Can you reproduce this issue with the beta channel? Yes
Can you reproduce this issue with the dev channel? Yes
Can you reproduce this issue with the nightly channel? Yes

Other Additional Information:

Does the issue resolve itself when disabling Brave Shields? No, since it happens on every page and brave shields doesn't even get loaded
Does the issue resolve itself when disabling Brave Rewards? No, since it happens on every page and brave rewards doesn't even get loaded
Is the issue reproducible on the latest version of Chrome? No. Chrome works without problems. On Chromium I h ave the same problem though

cyb3rw0lf commented 5 years ago

I have exactly the same issues, was working until few hours ago. Not sure if it did some automatic update

TrogdorsArm commented 5 years ago

Same issue. Was using Brave this morning, now all I get is the Aw, Snap! for everything.

iamajaz commented 5 years ago

Same issue for me on my corporate laptop.

I'm currently using Symantec Endpoint Protection and added the application to exception, but that doesn't help either.

Chrome, firefox & IE work perfectly fine though.

ejames12 commented 5 years ago

Same issue here. May be chrome related as when I updated chrome just now I now have the same issue on both Brave and Chrome. IE works fine.

Can't get to anything, no settings, no crashes, no about nothing.

stromgald2 commented 5 years ago

Same. It started yesterday evening. Chrome and Brave stopped working. Tried Revo uninstall and removed everything rebooted and reinstalled - same problem. Manually delete folders in appdata roaming and local but that didn't help either. When i downloaded an old standalone version of brave from github it worked until i updated. Also a work pc w/ Symantec so i cant test disabling antivirus.

Techguyprivate commented 5 years ago

symantec antivirus is the problem, I think

daniel0x00 commented 5 years ago

Same here. Nothing works, cannot open even brave://crashes or any brave://* site. It happened after the upgrade to the new version. I also have Symantec and I'm under a corporate environment (maybe proxy related problem). Chrome and Egde Chromium work well.

dbarwikowski commented 5 years ago

After disabling Symantec with smc -stop Brave is still not working

bsclifton commented 5 years ago

+1 from @threedaysmore via https://github.com/brave/brave-browser/issues/6635

Ever since the upgrade at the end of last week (normal release channel) any tab I try to open (even settings or About Brave) crash with the "Aw snap" page.

the-icarus commented 5 years ago

It seems, that this issue is related to a new functionality in Chromium called RendererCodeIntegrity. As a workaround I added the following flag --disable-features=RendererCodeIntegrity when launching the brave.exe binary. Afterwards the browser starts and was not showing the "Aw Snap" page.

JuanCMC commented 5 years ago

It seems, that this issue is related to a new functionality in Chromium called RendererCodeIntegrity. As a workaround I added the following flag --disable-features=RendererCodeIntegrity when launching the brave.exe binary. Afterwards the browser starts and was not showing the "Aw Snap" page.

I also have Sysmatec Endpoint, had the same problem for 5 days and this fixed the crashes.

daniel0x00 commented 5 years ago

It seems, that this issue is related to a new functionality in Chromium called RendererCodeIntegrity. As a workaround I added the following flag --disable-features=RendererCodeIntegrity when launching the brave.exe binary. Afterwards the browser starts and was not showing the "Aw Snap" page.

I tried this approach, didn't work for me. Both by calling it from Win+R as well as calling it from PowerShell: Start-Process -FilePath 'brave.exe' -ArgumentList '--disable-features=RendererCodeIntegrity'

kobelobster commented 5 years ago

@daniel0x00

I added it to the shortcut target

and for me it fixes the issue. But @the-icarus what exactly does that flag do?

ejames12 commented 5 years ago

It seems, that this issue is related to a new functionality in Chromium called RendererCodeIntegrity. As a workaround I added the following flag --disable-features=RendererCodeIntegrity when launching the brave.exe binary. Afterwards the browser starts and was not showing the "Aw Snap" page.

I also have Sysmatec Endpoint, had the same problem for 5 days and this fixed the crashes.

This hasn't worked for me either, anything else you did?

nbonamy commented 5 years ago

Known to Symantec: https://support.symantec.com/us/en/article.tech256047.html The regedit fix could be more convenient. Need to translate to Brave though.

the-icarus commented 5 years ago

@ejames12 no, just added this flag and brave was working again.

@tzfrs as far as I understood, the Code Integrity feature is made by Microsoft and Chromium is using it to prevent loading unsigned modules during rendering. This flag will disable the new functionality.

daniel0x00 commented 5 years ago

Known to Symantec: https://support.symantec.com/us/en/article.tech256047.html The regedit fix could be more convenient. Need to translate to Brave though.

The value of my RendererCodeIntegrityEnabled attribute was already 0. So in other words, I don't think this is not the problem.

daniel0x00 commented 5 years ago

A colleague of mine told me this trick, which worked for me. Enable 'Compatibility with Windows 8' and all of the sudden the browser works again:

rebron commented 5 years ago

@Brave-Matt can we get Brave article/pointer to this doc https://support.symantec.com/us/en/article.tech256047.html on community or help.

isochronous commented 4 years ago

I just ran into this problem again for some reason on the latest version of Brave, and found that enabling Windows 8 compatibility mode fixed it.

jioblack commented 4 years ago

I ran into this problem and enabling compatibility mode for both chrome and brave browser fixed it. You might also "Run compatibility troubleshooter" which does the same thing.

desmonk commented 4 years ago

Ran into this issue recently and I don't have Symantec Endpoint or any AV. Tried all options here but just crashes within 1-5 minutes. Particularly when I try to upload data, this happens way quickly. Windows 10 - 32 bit - 1909

rebron commented 4 years ago

@desmonk Can you go into brave://crashes and send the crash report and post the crash id here? If you'd like, you can also set the pref to send crash reports automatically to Brave.

desmonk commented 4 years ago

I got this one: crash report

@rebron Any suggestion?

DustVoice commented 4 years ago

I have the same error on linux (Arch Linux, Kernel version 5.5.4.arch1-1, package brave-bin from the AUR, with brave --version = 79.1.2.43) so it shouldn't be neccessarily symantec related, as my system doesn't have anything comparable! The page that this error occurs the most on is Reddit! Even in an Incognito tab... I also deleted my cache and cookies, but the problem still persists. It might also be worth mentioning that the error just suddenly appeared, with no foreshadowing whatsoever.

DustVoice commented 4 years ago

Even the support article crashes... I even deleted everything under the "Advanced" tab.

This error makes using brave completely useless for now, as I can't even open a majority of pages and even YouTube crashes from time to time...

MartinSeeler commented 4 years ago

This happens to me as well, can't use it.

❯ brave --version
Brave Browser 79.1.2.43 unknown
❯ uname -r
5.5.7-arch1-1

sohahm commented 4 years ago

The following solutions have been tested and working fine as of now.

Brave Browser

Key: HKEY_LOCAL_MACHINE\Software\Policies\BraveSoftware\Brave
Name: RendererCodeIntegrityEnabled 
Type: DWORD (32-bit) 
Value: 0

Chrome Browser

Key: HKLM\Software\Policies\Google\Chrome
Name: RendererCodeIntegrityEnabled 
Type: DWORD (32-bit) 
Value: 0

Another solution is to add --disable-features=RendererCodeIntegrity with shortcut target i.e. "C:\Program Files (x86)\BraveSoftware\Brave-Browser-Beta\Application\brave.exe" --disable-features=RendererCodeIntegrity

DustVoice commented 4 years ago

As we (@MartinSeeler and I) mentioned, we're on Arch Linux, so unfortunately the fixes for Windows won't work. I also tried starting brave with your command line parameter, but at least for me this didn't resolve the problem.

MartinSeeler commented 4 years ago

@sohahm I've tried it as well, but like @DustVoice, this "fix" does not work.

Opening Brave and launching YouTube will instantly crash the browser. Here is the output:

❯ brave --disable-features=RendererCodeIntegrity
error: could not open file /var/lib/pacman/local/firefox-74.0-2/desc: No such file or directory
[5577:5577:0310/155510.278856:ERROR:vaapi_wrapper.cc(417)] vaInitialize failed: unknown libva error
[5577:5577:0310/155510.385947:ERROR:viz_main_impl.cc(180)] Exiting GPU process due to errors during initialization
[5643:5643:0310/155510.422961:ERROR:vaapi_wrapper.cc(417)] vaInitialize failed: unknown libva error
[5643:5643:0310/155510.423208:ERROR:gl_implementation.cc(282)] Failed to load /usr/lib/brave-bin/swiftshader/libGLESv2.so: /usr/lib/brave-bin/swiftshader/libGLESv2.so: Kann die Shared-Object-Datei nicht öffnen: Datei oder Verzeichnis nicht gefunden
[5643:5643:0310/155510.425826:ERROR:viz_main_impl.cc(180)] Exiting GPU process due to errors during initialization
[5549:5598:0310/155510.470010:ERROR:dat_file_util.cc(22)] GetDATFileData: the dat file is not found or corrupted /home/chasmo/.config/BraveSoftware/Brave-Browser/jmomcjcilfpbaaklkifaijjcnancamde/1.0.506/rs-E71426E7-E898-401C-A195-177945415F38.dat
[5649:5649:0310/155510.474539:ERROR:vaapi_wrapper.cc(417)] vaInitialize failed: unknown libva error
[5549:5549:0310/155510.478282:ERROR:ad_block_base_service.cc(197)] Could not obtain ad block data
[5649:5649:0310/155510.482598:ERROR:gpu_channel_manager.cc(450)] ContextResult::kFatalFailure: Failed to create shared context for virtualization.
[5651:1:0310/155518.353592:ERROR:child_process_sandbox_support_impl_linux.cc(79)] FontService unique font name matching request did not receive a response.
[5651:1:0310/155518.353792:ERROR:child_process_sandbox_support_impl_linux.cc(79)] FontService unique font name matching request did not receive a response.
[5651:1:0310/155518.354337:ERROR:child_process_sandbox_support_impl_linux.cc(79)] FontService unique font name matching request did not receive a response.
[5651:1:0310/155518.354656:ERROR:child_process_sandbox_support_impl_linux.cc(79)] FontService unique font name matching request did not receive a response.
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0230
[5549:5549:0310/155610.333683:ERROR:gcm_channel_status_request.cc(145)] GCM channel request failed.

Based on the seccomp-bpf error and this bug report, I've tried it with brave --no-sandbox which does seem to work for me for now.

sohahm commented 4 years ago

@MartinSeeler Have you tried Brave Beta?

DustVoice commented 4 years ago

I for my part haven't tried Brave Beta, as I work on tight schedules and don't have time to search hours for a fix, which is why I'm using firefox as my main webbrowser atm, but if I find the time, I will try it out and report back.

MartinSeeler commented 4 years ago

@sohahm will try beta and give you feedback @DustVoice have you tried my suggest with brave --no-sandbox ?

DustVoice commented 4 years ago

Yes I tried using --no-sandbox, as I had to use this parameter on my previous Ubuntu machine, in order to make the snap package work. It seems to make the issue go away or at least not prominent to me. But I would recon that this shouldn't be the way this error is handled.

MartinSeeler commented 4 years ago

@sohahm The brave-beta seems to work. No crash so far.

❯ brave-beta --version
Brave Browser 80.1.5.105 unknown

guifel commented 4 years ago

The issue with the "Aw, Snap!" started to appear for me on Ubuntu after upgrading from Ubuntu 18 to 20. Note that I ran into it only on more demanding pages like Youtube,Google Meet, Facebook.

Chrome seems unaffected.

The message I see in the console is:

../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0230

The issue did not get solved with the flag --disable-features=RendererCodeIntegrity

guifel commented 4 years ago

My Brave installation was out of date.. Brave was not updating because somehow the brave apt repo was gone. I added it back and the issue is gone: https://brave-browser.readthedocs.io/en/latest/installing-brave.html#linux

silashayri commented 4 years ago

The following solutions have been tested and working fine as of now.

Brave Browser
Key: HKEY_LOCAL_MACHINE\Software\Policies\BraveSoftware\Brave
Name: RendererCodeIntegrityEnabled 
Type: DWORD (32-bit) 
Value: 0
Chrome Browser
Key: HKLM\Software\Policies\Google\Chrome
Name: RendererCodeIntegrityEnabled 
Type: DWORD (32-bit) 
Value: 0
Another solution is to add --disable-features=RendererCodeIntegrity with shortcut target i.e. "C:\Program Files (x86)\BraveSoftware\Brave-Browser-Beta\Application\brave.exe" --disable-features=RendererCodeIntegrity

It works for me. I created the releated path in regedit and boom! Brave is working well. Thanks

ryanbr commented 3 years ago

Just a followup @guifel @silashayri @MartinSeeler @DustVoice @kobelobster @JuanCMC

Is this still an issue with the current release of Brave (Version 1.21.77) ?

tybor commented 3 years ago

Still a issue, even with --disable-features=RendererCodeIntegrity. Each and every brave tab, even settings crashes after few seconds. On the shell the error is ../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:CRASHING:seccomp-bpf failure in syscall 0230 I'm on Debian, x64, package version 1.2.43, Chromium: 79.0.3945.130 (Official Build) (64-bit)

AntiSol commented 3 years ago

I have a similar issue. Opening youtube doesn't instantly crash the tab, it waits about 5 seconds until just after the page has finished loading.

here's my output:

[1754045:1754045:0816/232620.531246:ERROR:vaapi_wrapper.cc(982)] vaQuerySurfaceAttributes failed, VA error: invalid parameter
[1754045:1754045:0816/232620.531390:ERROR:vaapi_wrapper.cc(939)] FillProfileInfo_Locked failed for va_profile VAProfileH264Main and entrypoint VAEntrypointVLD
[1754045:1754045:0816/232620.531504:ERROR:vaapi_wrapper.cc(982)] vaQuerySurfaceAttributes failed, VA error: invalid parameter
[1754045:1754045:0816/232620.531719:ERROR:vaapi_wrapper.cc(939)] FillProfileInfo_Locked failed for va_profile VAProfileH264High and entrypoint VAEntrypointVLD
Failed to parse JSON adblock resources: EOF while parsing a value at line 1 column 0
[1754020:1754020:0816/232625.703542:ERROR:CONSOLE(1)] "[Shields]: Can't request shields panel data. Error: No tab url specified", source: chrome-extension://mnojpmjdmbbfmejpflffifhffcmidifd/out/brave_extension_background.bundle.js (1)
[1754020:1754020:0816/232625.703633:ERROR:CONSOLE(1)] "[Shields]: Can't request shields panel data. Error: No tab url specified", source: chrome-extension://mnojpmjdmbbfmejpflffifhffcmidifd/out/brave_extension_background.bundle.js (1)

#
# Fatal error in , line 0
# Fatal process out of memory: Failed to reserve memory for new V8 Isolate
#
#
#
#FailureMessage Object: 0x7f9e504011c0#0 0x557640c93309 <unknown>

As far as I can see adding the params makes no difference at all

AntiSol commented 3 years ago

I think I've figured this out, other Linux users might check / try this.

I had ulimit -v set to 16GB. Apparently brave was trying to allocate more than 16gb of memory?

to check, do 'ulimit -v' on the command line. If you get something other than 'unlimited', take a look in /etc/security/limits.conf and limits.conf.d. make sure the 'as' item (address space limit) is unlimited (not sure what actual limit brave needs? You'd think 16GB would be enough, right? ;) )

I had to reboot to get it to take effect. But now the issue seems to be solved.

brave / brave-browser