Re: Chromium/Buster constantly crashing
On 08/27/2021 09:30 AM, Ottavio Caruso wrote:
> Hi,
>
> $ uname -a
> Linux e130 4.19.0-14-amd64 #1 SMP Debian 4.19.171-2 (2021-01-30) x86_64 GNU/Linux
> $ cat /etc/debian_version
> 10.2
> $ chromium --version
> Chromium 90.0.4430.212 built on Debian 10.9, running on Debian 10.2
>
> For the last couple of weeks, Chromium has been constantly crashing. I've done the obvious troubleshooting (removing ~/.cache/chromium, deleting and recreating a new profile, purging and reinstalling the application, apt-get upgrade) to no avail.
>
>
> This is what I get after the crash, after launching chromium from the terminal:
>
> [7966:7966:0827/075828.005688:ERROR:gpu_init.cc(426)] Passthrough is not supported, GL is disabled
> Fontconfig error: Cannot load default config file
> Fontconfig error: Cannot load default config file
> Received signal 11 SEGV_MAPERR 000000000000
> #0 0x55f90e2ed6b9 (/usr/lib/chromium/chromium+0x5b4b6b8)
> #1 0x55f90e259923 (/usr/lib/chromium/chromium+0x5ab7922)
> #2 0x55f90e2ed241 (/usr/lib/chromium/chromium+0x5b4b240)
> #3 0x7fcbdc0b1730 (/lib/x86_64-linux-gnu/libpthread-2.28.so+0x1272f)
> #4 0x55f90cec56de (/usr/lib/chromium/chromium+0x47236dd)
> #5 0x55f90cec5b4f (/usr/lib/chromium/chromium+0x4723b4e)
> #6 0x55f90ceca741 (/usr/lib/chromium/chromium+0x4728740)
> #7 0x55f9106039c6 (/usr/lib/chromium/chromium+0x7e619c5)
> #8 0x55f90c1a571a (/usr/lib/chromium/chromium+0x3a03719)
> #9 0x55f90e2aedd2 (/usr/lib/chromium/chromium+0x5b0cdd1)
> #10 0x55f90e2c0797 (/usr/lib/chromium/chromium+0x5b1e796)
> #11 0x55f90e2c0494 (/usr/lib/chromium/chromium+0x5b1e493)
> #12 0x55f90e2728f6 (/usr/lib/chromium/chromium+0x5ad08f5)
> #13 0x55f90e2c1069 (/usr/lib/chromium/chromium+0x5b1f068)
> #14 0x55f90e295730 (/usr/lib/chromium/chromium+0x5af372f)
> #15 0x55f90e45ce91 (/usr/lib/chromium/chromium+0x5cbae90)
> #16 0x55f90c412912 (/usr/lib/chromium/chromium+0x3c70911)
> #17 0x55f90c4145e2 (/usr/lib/chromium/chromium+0x3c725e1)
> #18 0x55f90c40fbb9 (/usr/lib/chromium/chromium+0x3c6dbb8)
> #19 0x55f90e2330b2 (/usr/lib/chromium/chromium+0x5a910b1)
> #20 0x55f90e232c2c (/usr/lib/chromium/chromium+0x5a90c2b)
> #21 0x55f90e2305c4 (/usr/lib/chromium/chromium+0x5a8e5c3)
> #22 0x55f90e230e9e (/usr/lib/chromium/chromium+0x5a8ee9d)
> #23 0x55f90b603193 ChromeMain
> #24 0x7fcbd69cd09b __libc_start_main
> #25 0x55f90b60302a _start
> r8: 00007fcbd6b64c40 r9: 000055f9163a1360 r10: 0000000000000006 r11: 00007fcbd6b64c40
> r12: 000055f91a009288 r13: 00007fffda732b78 r14: 000055f91a009270 r15: 000055f91a009270
> di: 0000000000000000 si: 0000000000000080 bp: 00007fffda732bb0 bx: 000055f9160ac480
> dx: 000055f91b3a3024 ax: 000055f91651f070 cx: 0000000000000000 sp: 00007fffda732b40
> ip: 000055f90cec56de efl: 0000000000010246 cgf: 002b000000000033 erf: 0000000000000004
> trp: 000000000000000e msk: 0000000000000000 cr2: 0000000000000000
> [end of stack trace]
> Calling _exit(1). Core file will not be generated.
>
>
> Anything I can get from that output?
>
That it's chromium and that it crashed.
Try palemoon. it's more performant and less broken
than both chromium and newer (chromium-based)firefox.
Reply to: