Brave Browser crashing after 2-3 minutes of idle (sync problem?)

Brave Browser 1.11.104 crashing on Mint Linux just after 2-3 minutes of idle (no page opened)

Brave Version: 1.11.104

Additional Information:

EDIT: Browser stopped crashing after sync flag disabled.

System information:
Kernel: 5.4.0-42-generic x86_64 bits: 64 compiler: gcc v: 7.5.0
Desktop: MATE 1.22.2 wm: marco dm: LightDM Distro: Linux Mint 19.3 Tricia
base: Ubuntu 18.04 bionic
Machine:
Type: Desktop System: Gigabyte product: X570 UD v: N/A serial:
Mobo: Gigabyte model: X570 UD v: x.x serial: UEFI: American Megatrends v: F11
CPU: Topology: 8-Core model: AMD Ryzen 7 3700X bits: 64 type: MT MCP arch: Zen
L2 cache: 4096 KiB
Graphics: Device-1: NVIDIA GP107GL [Quadro P400] driver: nouveau v: kernel bus ID: 07:00.0
chip ID: 10de:1cb3
Display: x11 server: X.Org 1.20.8 driver: modesetting FAILED: nvidia
unloaded: fbdev,vesa compositor: marco resolution: 1920x1200~60Hz, 1600x1200~60Hz
OpenGL: renderer: llvmpipe (LLVM 10.0.0 128 bits) v: 3.3 Mesa 20.0.8 compat-v: 3.1
direct render: Yes

Log from terminal:
$ brave-browser
[19659:19695:0806/231721.627195:ERROR:nigori_sync_bridge_impl.cc(810)] Encryption Keys datatype error was encountered: NigoriSpecifics is not valid.
libva error: va_getDriverName() failed with unknown libva error,driver_name=(null)
[19688:19688:0806/231721.675475:ERROR:vaapi_wrapper.cc(511)] vaInitialize failed: unknown libva error
[19688:19688:0806/231721.688862:ERROR:viz_main_impl.cc(150)] Exiting GPU process due to errors during initialization
[19659:19659:0806/231721.848827:ERROR:sharing_service.cc(261)] Device registration failed with fatal error
nvc0_screen_create:1111 - Error allocating PGRAPH context for M2MF: -16
[19659:19659:0806/231721.894959: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)
libva error: /usr/lib/x86_64-linux-gnu/dri/nouveau_drv_video.so init failed
[19788:19788:0806/231721.904209:ERROR:vaapi_wrapper.cc(511)] vaInitialize failed: resource allocation failed
[19659:19659:0806/231721.950902:ERROR:CONSOLE(0)] “Unchecked runtime.lastError: Cannot access contents of url “chrome://newtab/”. Extension manifest must request permission to access this host.”, source: chrome-extension://mnojpmjdmbbfmejpflffifhffcmidifd/_generated_background_page.html (0)
[19659:19659:0806/231722.080536:ERROR:CONSOLE(16)] “callbackList.fetch-sync-records is not a function”, source: chrome-extension://nomlkjnggnifocmealianaaiobmebgil/extension/background.js (16)
[19659:19659:0806/231722.083967:ERROR:CONSOLE(0)] “Error in event handler: TypeError: callbackList.send-sync-records is not a function
at chrome-extension://nomlkjnggnifocmealianaaiobmebgil/extension/background.js:57:36”, source: chrome-extension://nomlkjnggnifocmealianaaiobmebgil/_generated_background_page.html (0)
[19659:19659:0806/231722.085339:ERROR:CONSOLE(0)] “Error in event handler: TypeError: callbackList.send-sync-records is not a function
at chrome-extension://nomlkjnggnifocmealianaaiobmebgil/extension/background.js:57:36”, source: chrome-extension://nomlkjnggnifocmealianaaiobmebgil/_generated_background_page.html (0)
[19659:19659:0806/231722.085679:ERROR:CONSOLE(0)] “Error in event handler: TypeError: callbackList.send-sync-records is not a function
at chrome-extension://nomlkjnggnifocmealianaaiobmebgil/extension/background.js:57:36”, source: chrome-extension://nomlkjnggnifocmealianaaiobmebgil/_generated_background_page.html (0)
[19659:19659:0806/231726.761968:ERROR:CONSOLE(0)] “Unchecked runtime.lastError: Cannot access contents of url “chrome://settings/help”. Extension manifest must request permission to access this host.”, source: chrome-extension://mnojpmjdmbbfmejpflffifhffcmidifd/_generated_background_page.html (0)
[19690:19714:0806/231822.166911:ERROR:broker_posix.cc(40)] Recvmsg error: Connection reset by peer (104)
/usr/bin/brave-browser: line 48: 19659 Segmentation fault (memory dump) “HERE/brave" "@”

1 Like

Brave Sync v2 is coming and which I believe will not crash the browser – that’s the reason the current Sync is disabled. Should be available in the next major update.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.