Bug 28631 - Chromium browser crash after few seconds
Summary: Chromium browser crash after few seconds
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: High major
Target Milestone: ---
Assignee: Christiaan Welvaart
QA Contact:
URL: https://bugs.chromium.org/p/chromium/...
Whiteboard: MGA8TOO
Keywords:
Depends on: 28702 28732
Blocks:
  Show dependency treegraph
 
Reported: 2021-03-22 17:52 CET by Daniel Tartavel
Modified: 2021-04-14 16:26 CEST (History)
8 users (show)

See Also:
Source RPM: chromium-browser-stable-89.0.4389.90-1.mga9.src.rpm
CVE:
Status comment:


Attachments

Description Daniel Tartavel 2021-03-22 17:52:49 CET
Description of problem:


Version-Release number of selected component (if applicable):
89.0.4389.90-1

Steps to Reproduce:
1.launch chromium browser
2. wait some seconds

logs when launching from shell:

[154535:154535:0322/172452.526628:ERROR:allowlist.cc(66)] Component extension with manifest resource id 11690 not in allowlist and is not being loaded as a result.
[154535:154535:0322/172452.526741:ERROR:allowlist.cc(66)] Component extension with manifest resource id 11691 not in allowlist and is not being loaded as a result.
[154565:154565:0322/172452.894730:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu-process.
Received signal 11 SEGV_MAPERR 000000000054
#0 0x55f346803119 base::debug::CollectStackTrace()
#1 0x55f346752176 base::debug::StackTrace::StackTrace()
#2 0x55f346802b59 base::debug::(anonymous namespace)::StackDumpSignalHandler()
#3 0x7fb33e1f6a70 (/usr/lib64/libpthread-2.33.so+0x12a6f)
#4 0x7fb33a0d50f6 __GI___strlen_sse2
#5 0x55f34923b25a cast_channel::KeepAliveHandler::HandleMessage()
#6 0x55f34923ab0c cast_channel::KeepAliveDelegate::OnMessage()
#7 0x55f3492395ac cast_channel::CastTransportImpl::DoReadCallback()
#8 0x55f3492399bf cast_channel::CastTransportImpl::OnReadResult()
#9 0x55f34923c1ae cast_channel::MojoDataPump::ReceiveMore()
#10 0x55f34702467d mojo::SimpleWatcher::OnHandleReady()
#11 0x55f3467c02f2 base::TaskAnnotator::RunTask()
#12 0x55f3467d6fbb base::sequence_manager::internal::ThreadControllerWithMessagePumpImpl::DoWorkImpl()
#13 0x55f3467d7ca6 base::sequence_manager::internal::ThreadControllerWithMessagePumpImpl::DoWork()
#14 0x55f346835cd1 base::MessagePumpLibevent::Run()
#15 0x55f3467d61b0 base::sequence_manager::internal::ThreadControllerWithMessagePumpImpl::Run()
#16 0x55f34679f7ec base::RunLoop::Run()
#17 0x55f343c1045a content::BrowserProcessSubThread::IOThreadRun()
#18 0x55f3467ebf28 base::Thread::ThreadMain()
#19 0x55f346816866 base::(anonymous namespace)::ThreadFunc()
#20 0x7fb33e1eccba start_thread
#21 0x7fb33a13100f __GI___clone
  r8: 0000000000000000  r9: 0000000000000000 r10: 0000000000000000 r11: 0000000000000007
 r12: 00007fb3040c6540 r13: 0000000000000054 r14: 00007fb317ffe070 r15: 00007fb317ffe2d8
  di: 0000000000000054  si: ffffd64049c9f5c0  bp: 00007fb317ffde00  bx: 00007fb3040caf60
  dx: 0000000000000019  ax: 0000000000000054  cx: 0000000000000054  sp: 00007fb317ffddc8
  ip: 00007fb33a0d50f6 efl: 0000000000010293 cgf: 002b000000000033 erf: 0000000000000004
 trp: 000000000000000e msk: 0000000000000000 cr2: 0000000000000054
[end of stack trace]
Calling _exit(1). Core file will not be generated.
Comment 1 Lewis Smith 2021-03-23 21:35:35 CET
Thank you for the report.
The Cauldron version here is currently the same as for M8, but I do not have the time just now to try it. Will do tomorrow unless Aurélien gets here first.

CC: (none) => ouaurelien

Comment 2 Rolf Pedersen 2021-03-24 01:09:28 CET
On 64-bit MGA8 Official, chromium crashes in apparently same way, here:

[rolf@x570i ~]$ chromium-browser 
[1327935:1327935:0323/162220.025349:ERROR:gl_initializer_linux_x11.cc(124)] eglGetProcAddress not found.
[1327935:1327935:0323/162220.026552:ERROR:viz_main_impl.cc(150)] Exiting GPU process due to errors during initialization
[1326956:1326956:0323/162220.047319:ERROR:allowlist.cc(66)] Component extension with manifest resource id 11690 not in allowlist and is not being loaded as a result.
[1326956:1326956:0323/162220.047399:ERROR:allowlist.cc(66)] Component extension with manifest resource id 11691 not in allowlist and is not being loaded as a result.
Received signal 11 SEGV_MAPERR 000000000054
#0 0x56188c84d079 base::debug::CollectStackTrace()
#1 0x56188c79c0d6 base::debug::StackTrace::StackTrace()
#2 0x56188c84cab9 base::debug::(anonymous namespace)::StackDumpSignalHandler()
#3 0x7f725b1fd170 (/usr/lib64/libpthread-2.32.so+0x1316f)
#4 0x7f72571a2691 __strlen_avx2
#5 0x56188f28520a cast_channel::KeepAliveHandler::HandleMessage()
#6 0x56188f284abc cast_channel::KeepAliveDelegate::OnMessage()
#7 0x56188f28355c cast_channel::CastTransportImpl::DoReadCallback()
#8 0x56188f28396f cast_channel::CastTransportImpl::OnReadResult()
#9 0x56188f28615e cast_channel::MojoDataPump::ReceiveMore()
#10 0x56188d06e62d mojo::SimpleWatcher::OnHandleReady()
#11 0x56188c80a252 base::TaskAnnotator::RunTask()
#12 0x56188c820f1b base::sequence_manager::internal::ThreadControllerWithMessagePumpImpl::DoWorkImpl()
#13 0x56188c821c06 base::sequence_manager::internal::ThreadControllerWithMessagePumpImpl::DoWork()
#14 0x56188c87fc71 base::MessagePumpLibevent::Run()
#15 0x56188c820110 base::sequence_manager::internal::ThreadControllerWithMessagePumpImpl::Run()
#16 0x56188c7e974c base::RunLoop::Run()
#17 0x561889c5a41a content::BrowserProcessSubThread::IOThreadRun()
#18 0x56188c835e88 base::Thread::ThreadMain()
#19 0x56188c860806 base::(anonymous namespace)::ThreadFunc()
#20 0x7f725b1f2dea start_thread
#21 0x7f7257142fff __GI___clone
  r8: 0000000000000000  r9: 0000000000000000 r10: 00007fff1f5bd080 r11: 00007fff1f5bd090
 r12: 00007f722805c6d0 r13: 0000000000000054 r14: 00007f7249167070 r15: 00007f72491672d8
  di: 0000000000000054  si: 0000561893da9fc7  bp: 00007f7249166e00  bx: 00007f722815e0d0
  dx: 0000000000000054  ax: 0000000000000100  cx: 0000000000000014  sp: 00007f7249166dc8
  ip: 00007f72571a2691 efl: 0000000000010283 cgf: 002b000000000033 erf: 0000000000000004
 trp: 000000000000000e msk: 0000000000000000 cr2: 0000000000000054
[end of stack trace]
Calling _exit(1). Core file will not be generated.
[rolf@x570i ~]$

[rolf@x570i ~]$ rpm -qa|grep chromium
chromium-browser-stable-89.0.4389.90-1.mga8

I reverted to the last version:

[rolf@x570i ~]$ sudo rpm -Uvh --oldpackage http://mirrors.kernel.org/mageia/distrib/8/x86_64/media/core/updates/chromium-browser-stable-88.0.4324.182-1.mga8.x86_64.rpm

That doesn't crash, is usable, but I seem to have lost synced passwords and bookmarks.  Not sure what's happened/happening, tried various such as user addition, password import, log-in with google credentials, typical hammering, left somewhere in a limbo of mangled config files, I reckon.  At least, it doesn't crash, started from konsole, it reports, until closed in gui:

[rolf@x570i ~]$ chromium-browser 
[1352273:1352273:0323/162936.709755:ERROR:gl_initializer_linux_x11.cc(121)] eglGetProcAddress not found.
[1352273:1352273:0323/162936.711276:ERROR:viz_main_impl.cc(150)] Exiting GPU process due to errors during initialization
[1352233:1352262:0323/162936.723752:ERROR:media_history_store.cc(379)] Failed to create or update the media history store.
[1352233:1352287:0323/162936.732112:ERROR:login_database.cc(641)] Password store database is too new, kCurrentVersionNumber=28, GetCompatibleVersionNumber=29
[1352233:1352287:0323/162936.732245:ERROR:password_store_default.cc(39)] Could not create/open login database.
[1352233:1352263:0323/162936.744482:ERROR:login_database.cc(641)] Password store database is too new, kCurrentVersionNumber=28, GetCompatibleVersionNumber=29
[1352233:1352263:0323/162936.745546:ERROR:password_store_default.cc(39)] Could not create/open login database.
[1352276:1352309:0323/163838.434689:ERROR:ssl_client_socket_impl.cc(962)] handshake failed; returned -1, SSL error code 1, net_error -200
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile

[rolf@x570i ~]$

CC: (none) => rolfpedersen

Comment 3 Dave Hodgins 2021-03-24 07:32:12 CET
$ rpm -q chromium-browser-stable 
chromium-browser-stable-89.0.4389.90-1.mga8
is working for me in a Mageia 8 x86-64 install under ...
$ env|grep DESKTOP
DESKTOP_SESSION=/usr/share/xsessions/01plasma
XDG_SESSION_DESKTOP=KDE
XDG_CURRENT_DESKTOP=KDE
$ lspcidrake -v|grep ^Card
Card:ATI Volcanic Islands and later (amdgpu): Advanced Micro Devices, Inc. [AMD/ATI]|Renoir [DISPLAY_VGA] (vendor:1002 device:1636 subv:1043 subd:1e21) (rev: c6)
Card:NVIDIA GeForce 635 series and later: NVIDIA Corporation|TU106M [GeForce RTX 2060 Mobile] [DISPLAY_VGA] (vendor:10de device:1f15 subv:1043 subd:1e21) (rev: a1)

I'm using mageia-prime-0.4-12.mga8.nonfree for the multi card handling.

CC: (none) => davidwhodgins

Comment 4 Rolf Pedersen 2021-03-24 14:04:54 CET
[rolf@x570i ~]$ env|grep DESKTOP
DESKTOP_SESSION=/usr/share/xsessions/01plasma
XDG_SESSION_DESKTOP=KDE
XDG_CURRENT_DESKTOP=KDE
[rolf@x570i ~]$ lspcidrake -v|grep ^Card
Card:ATI Volcanic Islands and later (amdgpu): Advanced Micro Devices, Inc. [AMD/ATI]|Picasso [DISPLAY_VGA] (vendor:1002 device:15d8 subv:1043 subd:876b) (rev: c8)
[rolf@x570i ~]$

Attention to video hardware reminds me of an inexplicable apparent correlation between unplugging a secondary screen from this ASUS Rog Strix x570-i Gaming and solving "Bug 27377 - VLC plays audio but not video" for me, apparently:  https://bugs.mageia.org/show_bug.cgi?id=27377#c22

Thanks.
Comment 5 Dave Hodgins 2021-03-24 15:35:21 CET
Please also try creating a new user, logging out, then in as the new user and
see if the crash happens there too. That will indicate if it's some non default
config file settings causing it to impact those systems but not mine.
Comment 6 Aurelian R 2021-03-24 16:54:21 CET
I can confirm an identical chromium-browser behavior as reported in both Mga8 and Cauldron on a different hardware, and a fresh user account doesn't fix it.

$ env|grep DESKTOP
DESKTOP_SESSION=/usr/share/xsessions/01plasma
XDG_SESSION_DESKTOP=KDE
XDG_CURRENT_DESKTOP=KDE

$ lspcidrake -v|grep ^Card
Card:NVIDIA GeForce 420 to GeForce 630: NVIDIA Corporation|GF116 [GeForce GTX 550 Ti] [DISPLAY_VGA] (vendor:10de device:1244 subv:19da subd:5194) (rev: a1)

$ inxi -SG
System:    Host: localhost Kernel: 5.10.25-desktop-1.mga8 x86_64 bits: 64 Desktop: KDE Plasma 5.20.4 Distro: Mageia 8 mga8 
Graphics:  Device-1: NVIDIA GF116 [GeForce GTX 550 Ti] driver: nvidia v: 390.141 
           Display: x11 server: Mageia X.org 1.20.10 driver: nvidia resolution: 1920x1200~60Hz 
           OpenGL: renderer: GeForce GTX 550 Ti/PCIe/SSE2 v: 4.6.0 NVIDIA 390.141 
$ inxi -SG
System:    Host: localhost Kernel: 5.11.8-desktop-1.mga9 x86_64 bits: 64 Desktop: KDE Plasma 5.21.3 Distro: Mageia 9 mga9 
Graphics:  Device-1: NVIDIA GF116 [GeForce GTX 550 Ti] driver: nvidia v: 390.141 
           Display: x11 server: Mageia X.org 1.20.10 driver: loaded: nvidia,v4l resolution: 1920x1200~60Hz 
           OpenGL: renderer: GeForce GTX 550 Ti/PCIe/SSE2 v: 4.6.0 NVIDIA 390.141

CC: (none) => arusanu

Comment 7 Rolf Pedersen 2021-03-25 14:00:09 CET
Logged in as user "test" in plasma or xfce, terminal output looks almost identical, to me.

plasma:

(chromium-browser:50785): Gtk-WARNING **: 05:17:04.648: Theme parsing error: gtk.css:3:33: Failed to import: Error opening file /home/test/.config/gtk-3.0/window_decorations.css: No such file or directory
[50785:50785:0325/051704.695939:ERROR:allowlist.cc(66)] Component extension with manifest resource id 11690 not in allowlist and is not being loaded as a result.
[50785:50785:0325/051704.696034:ERROR:allowlist.cc(66)] Component extension with manifest resource id 11691 not in allowlist and is not being loaded as a result.
[50816:50816:0325/051704.821748:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu-process.
Received signal 11 SEGV_MAPERR 000000000054
#0 0x56401b060079 base::debug::CollectStackTrace()
#1 0x56401afaf0d6 base::debug::StackTrace::StackTrace()
#2 0x56401b05fab9 base::debug::(anonymous namespace)::StackDumpSignalHandler()
#3 0x7f6bcc3e4170 (/usr/lib64/libpthread-2.32.so+0x1316f)
#4 0x7f6bc8389691 __strlen_avx2
#5 0x56401da9820a cast_channel::KeepAliveHandler::HandleMessage()
#6 0x56401da97abc cast_channel::KeepAliveDelegate::OnMessage()
#7 0x56401da9655c cast_channel::CastTransportImpl::DoReadCallback()
#8 0x56401da9696f cast_channel::CastTransportImpl::OnReadResult()
#9 0x56401da9915e cast_channel::MojoDataPump::ReceiveMore()
#10 0x56401b88162d mojo::SimpleWatcher::OnHandleReady()
#11 0x56401b01d252 base::TaskAnnotator::RunTask()
#12 0x56401b033f1b base::sequence_manager::internal::ThreadControllerWithMessagePumpImpl::DoWorkImpl()
#13 0x56401b034c06 base::sequence_manager::internal::ThreadControllerWithMessagePumpImpl::DoWork()
#14 0x56401b092c71 base::MessagePumpLibevent::Run()
#15 0x56401b033110 base::sequence_manager::internal::ThreadControllerWithMessagePumpImpl::Run()
#16 0x56401affc74c base::RunLoop::Run()
#17 0x56401846d41a content::BrowserProcessSubThread::IOThreadRun()
#18 0x56401b048e88 base::Thread::ThreadMain()
#19 0x56401b073806 base::(anonymous namespace)::ThreadFunc()
#20 0x7f6bcc3d9dea start_thread
#21 0x7f6bc8329fff __GI___clone
  r8: 0000000000000000  r9: 0000000000000000 r10: 00007fff0fb49080 r11: 00007fff0fb49090
 r12: 00007f6b9c002920 r13: 0000000000000054 r14: 00007f6bb27fb070 r15: 00007f6bb27fb2d8
  di: 0000000000000054  si: 00005640225bcfc7  bp: 00007f6bb27fae00  bx: 00007f6b9c0e4ec0
  dx: 0000000000000054  ax: 0000000000000100  cx: 0000000000000014  sp: 00007f6bb27fadc8
  ip: 00007f6bc8389691 efl: 0000000000010283 cgf: 002b000000000033 erf: 0000000000000004
 trp: 000000000000000e msk: 0000000000000000 cr2: 0000000000000054
[end of stack trace]
Calling _exit(1). Core file will not be generated.
[test@x570i ~]$ 

xfce:

[test@x570i ~]$ chromium-browser 

(chromium-browser:104975): Gtk-WARNING **: 05:26:10.855: Theme parsing error: gtk.css:3:33: Failed to import: Error opening file /home/test/.config/gtk-3.0/window_decorations.css: No such file or directory
[104975:104975:0325/052610.903083:ERROR:allowlist.cc(66)] Component extension with manifest resource id 11690 not in allowlist and is not being loaded as a result.
[104975:104975:0325/052610.903250:ERROR:allowlist.cc(66)] Component extension with manifest resource id 11691 not in allowlist and is not being loaded as a result.
[105005:105005:0325/052611.033490:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu-process.
Received signal 11 SEGV_MAPERR 000000000054
#0 0x55ba10c29079 base::debug::CollectStackTrace()
#1 0x55ba10b780d6 base::debug::StackTrace::StackTrace()
#2 0x55ba10c28ab9 base::debug::(anonymous namespace)::StackDumpSignalHandler()
#3 0x7ff221cb3170 (/usr/lib64/libpthread-2.32.so+0x1316f)
#4 0x7ff21dc58691 __strlen_avx2
#5 0x55ba1366120a cast_channel::KeepAliveHandler::HandleMessage()
#6 0x55ba13660abc cast_channel::KeepAliveDelegate::OnMessage()
#7 0x55ba1365f55c cast_channel::CastTransportImpl::DoReadCallback()
#8 0x55ba1365f96f cast_channel::CastTransportImpl::OnReadResult()
#9 0x55ba1366215e cast_channel::MojoDataPump::ReceiveMore()
#10 0x55ba1144a62d mojo::SimpleWatcher::OnHandleReady()
#11 0x55ba10be6252 base::TaskAnnotator::RunTask()
#12 0x55ba10bfcf1b base::sequence_manager::internal::ThreadControllerWithMessagePumpImpl::DoWorkImpl()
#13 0x55ba10bfdc06 base::sequence_manager::internal::ThreadControllerWithMessagePumpImpl::DoWork()
#14 0x55ba10c5bc71 base::MessagePumpLibevent::Run()
#15 0x55ba10bfc110 base::sequence_manager::internal::ThreadControllerWithMessagePumpImpl::Run()
#16 0x55ba10bc574c base::RunLoop::Run()
#17 0x55ba0e03641a content::BrowserProcessSubThread::IOThreadRun()
#18 0x55ba10c11e88 base::Thread::ThreadMain()
#19 0x55ba10c3c806 base::(anonymous namespace)::ThreadFunc()
#20 0x7ff221ca8dea start_thread
#21 0x7ff21dbf8fff __GI___clone
  r8: 0000000000000000  r9: 0000000000000000 r10: 00007ffd337f5080 r11: 00007ffd337f5090
 r12: 00007ff1ec133760 r13: 0000000000000054 r14: 00007ff1ffffe070 r15: 00007ff1ffffe2d8
  di: 0000000000000054  si: 000055ba18185fc7  bp: 00007ff1ffffde00  bx: 00007ff1ec08ebf0
  dx: 0000000000000054  ax: 0000000000000100  cx: 0000000000000014  sp: 00007ff1ffffddc8
  ip: 00007ff21dc58691 efl: 0000000000010283 cgf: 002b000000000033 erf: 0000000000000004
 trp: 000000000000000e msk: 0000000000000000 cr2: 0000000000000054
[end of stack trace]
Calling _exit(1). Core file will not be generated.
[test@x570i ~]$
Comment 8 Lewis Smith 2021-03-25 20:20:05 CET
Thanks particularly to Rolf for his extensive tests around this: comment 2 chromium-browser-stable-88.0.4324.182-1.mga8.x86_64.rpm working is important.
h/w details in comment 4.
Also to Dave & Aurélien for their additions.
Only Dave has no problem (comment 3, with H/W details).
Aurélien gave h/w details comment 6, both crashes.

@Daniel
Please give your video details from:
 $ inxi -SGxx
then we might see whether there is a graphics dependency.

Status: NEW => NEEDINFO
CC: (none) => lewyssmith

Comment 9 Aurelien Oudelet 2021-03-25 20:29:05 CET
(In reply to Lewis Smith from comment #8)
> Thanks particularly to Rolf for his extensive tests around this: comment 2
> chromium-browser-stable-88.0.4324.182-1.mga8.x86_64.rpm working is important.
> h/w details in comment 4.
> Also to Dave & Aurélien for their additions.
> Only Dave has no problem (comment 3, with H/W details).
> Aurélien gave h/w details comment 6, both crashes. <=== Lewis, this is not me ;)

But!

Already reported this when we did QA:

https://bugs.mageia.org/show_bug.cgi?id=28534#c3
https://bugs.mageia.org/show_bug.cgi?id=28534#c4

Mine errors were about:
[20513:20513:0312/103838.388164:ERROR:allowlist.cc(66)] Component extension with manifest resource id 11690 not in allowlist and is not being loaded as a result.
[20513:20513:0312/103838.388446:ERROR:allowlist.cc(66)] Component extension with manifest resource id 11691 not in allowlist and is not being loaded as a result.
[20543:20543:0312/103838.552602:ERROR:vaapi_wrapper.cc(1045)] vaQuerySurfaceAttributes failed, VA error: invalid parameter
[20543:20543:0312/103838.552725:ERROR:vaapi_wrapper.cc(993)] FillProfileInfo_Locked failed for va_profile VAProfileH264Main and entrypoint VAEntrypointVLD
[20543:20543:0312/103838.552788:ERROR:vaapi_wrapper.cc(1045)] vaQuerySurfaceAttributes failed, VA error: invalid parameter
[20543:20543:0312/103838.552824:ERROR:vaapi_wrapper.cc(993)] FillProfileInfo_Locked failed for va_profile VAProfileH264High and entrypoint VAEntrypointVLD
Received signal 11 SEGV_ACCERR 7f3df9ffc000

strace in https://bugs.mageia.org/show_bug.cgi?id=28534#c4

Note that like Rolf, http://mirrors.kernel.org/mageia/distrib/8/x86_64/media/core/updates/chromium-browser-stable-88.0.4324.182-1.mga8.x86_64.rpm
does not crash.

Severity: normal => major
Whiteboard: (none) => MGA8TOO
Priority: Normal => High

Comment 10 Lewis Smith 2021-03-25 21:18:41 CET
Forced into trying this horrid thing:
 chromium-browser-stable-89.0.4389.90-1.mga8.x86_64
$ inxi -Sxx -G
System:
  Host: localhost Kernel: 5.10.25-desktop-1.mga8 x86_64 bits: 64 
  compiler: gcc v: 10.2.1 Desktop: KDE Plasma 5.20.4 tk: Qt 5.15.2 
  wm: kwin_x11 dm: LightDM, LXDM Distro: Mageia 8 mga8 
Graphics:
  Device-1: AMD Wrestler [Radeon HD 7310] vendor: Acer Incorporated ALI 
  driver: radeon v: kernel bus ID: 00:01.0 chip ID: 1002:9809 
  Display: x11 server: Mageia X.org 1.20.10 compositor: kwin_x11 
  driver: ati,radeon,v4l resolution: 1366x768~60Hz s-dpi: 96 
  OpenGL: 
  renderer: AMD PALM (DRM 2.50.0 / 5.10.25-desktop-1.mga8 LLVM 11.0.1) 
  v: 3.3 Mesa 20.3.4 compat-v: 3.1 direct render: Yes

In my case, it worked (straight into the arms of Google..)

I think we must pass this to Christiaan (CC NicolasS, also recent committer).

Assignee: bugsquad => cjw
CC: lewyssmith => nicolas.salguero

Comment 11 Christiaan Welvaart 2021-03-25 21:53:18 CET
If it is the same crash that I'm seeing with my test builds:

Block the incoming cast traffic on the Mageia machine, e.g. by blocking all incoming traffic from the chromecast(-enabled) device by MAC address.

Of course this not a good option if you want to cast from the Mageia machine to the chromeast(-enabled) device.

We have "external components" disabled by making chromium's allow list empty. One of those extensions is the "CastExtension".
Comment 12 Daniel Tartavel 2021-03-26 19:51:06 CET
Hi Lewis,

# inxi -Sxx -G give this result:

System:    Host: espace.tuina Kernel: 5.11.6-desktop-4.mga9 x86_64 bits: 64 compiler: gcc v: 10.2.1 Console: tty pts/3 
           wm: kwin_x11 DM: SDDM Distro: Mageia 9 mga9 
Graphics:  Device-1: NVIDIA GK208B [GeForce GT 710] vendor: Micro-Star MSI driver: nvidia v: 460.67 bus-ID: 01:00.0 
           chip-ID: 10de:128b 
           Display: server: Mageia X.org 1.20.10 compositor: kwin_x11 driver: loaded: nvidia,v4l resolution: 1: 1920x1080~60Hz 
           2: 1920x1080~60Hz s-dpi: 94 
           OpenGL: renderer: GeForce GT 710/PCIe/SSE2 v: 4.6.0 NVIDIA 460.67 direct render: Yes
Comment 13 Aurelien Oudelet 2021-04-02 12:55:25 CEST
Same with Mageia 8, like comment 9

System:    Host: mageia.local Kernel: 5.10.27-desktop-1.mga8 x86_64 bits: 64 compiler: gcc v: 10.2.1 
           Desktop: KDE Plasma 5.20.4 tk: Qt 5.15.2 wm: kwin_x11 dm: SDDM Distro: Mageia 8 mga8 
Graphics:  Device-1: NVIDIA TU116 [GeForce GTX 1660 Ti] vendor: Gigabyte driver: nvidia v: 460.67 
           bus ID: 01:00.0 chip ID: 10de:2182 
           Display: x11 server: Mageia X.org 1.20.10 compositor: kwin_x11 driver: nvidia,v4l resolution: 
           1: 1920x1080 2: 1920x1080~60Hz s-dpi: 81 
           OpenGL: renderer: GeForce GTX 1660 Ti/PCIe/SSE2 v: 4.6.0 NVIDIA 460.67 direct render: Yes

Status: NEEDINFO => NEW

Aurelien Oudelet 2021-04-02 12:55:40 CEST

Depends on: (none) => 28702

Comment 14 Rolf Pedersen 2021-04-02 17:24:33 CEST
"Frantic hammering" IT method does not lend itself well to logging but here goes.

I've disabled all extensions,
turned off hardware acceleration (it was on),
Cleared browser data that was pre-selected by default:  browsing history, cookies and other site data, cached images and files, ... not deleting saved passwords and form data sorts of things that take a long time to create,
turned off a "developer" switch that I can't seem to find anymore,
reset all settings to default via the button by that name.

Newest chromium just crashes after close to 10 seconds open time, no matter any of these changes.

(In reply to Christiaan Welvaart from comment #11)
> If it is the same crash that I'm seeing with my test builds:
> 
> Block the incoming cast traffic on the Mageia machine, e.g. by blocking all
> incoming traffic from the chromecast(-enabled) device by MAC address.
> 
> Of course this not a good option if you want to cast from the Mageia machine
> to the chromeast(-enabled) device.
> 
> We have "external components" disabled by making chromium's allow list
> empty. One of those extensions is the "CastExtension".

I have an LG WebOS tv that shows up in "Cast" and an nvidia Shield that is sometimes there, sometimes not.  The configuration is, AFAICT, limited to choosing cast tab, cast desktop, cast file.  Ctrl-click does not de-select the chosen mode, so disabling cast does not happen, here.  Google search reveals other irritated people who have various serious problems with cast being turned on all the time and the typical un-responsive "help" from google, i.e. no apparent way to turn off cast in gui.

How do you

> Block the incoming cast traffic on the Mageia machine, e.g. by blocking all
> incoming traffic from the chromecast(-enabled) device by MAC address.

?

Thanks.
Comment 15 Christiaan Welvaart 2021-04-03 13:10:28 CEST
To block cast traffic I simply blocked all traffic from the cast-enabled device on the PC, since neither the PC nor the TV box acts as a server to the other:
  iptables -m mac -t raw -A PREROUTING --mac-source xx:xx:xx:xx:xx:xx -j DROP

with xx:xx:xx:xx:xx:xx the MAC address of the USB ethernet adapter I use for my Xiaomi Mi Box.

I tried changing several cast related settings in chromium, but nothing helped.


To debug this crash I think I need debug info, while gcc currently can't build chromium with debug info unless it's updated to the next version (gcc 11), or the changes outlined in the following patch are applied:

https://gcc.gnu.org/pipermail/gcc-patches/2020-December/560734.html
Nicolas Lécureuil 2021-04-05 23:45:21 CEST

Depends on: (none) => 28732

Comment 16 Rolf Pedersen 2021-04-07 19:12:15 CEST
(In reply to Christiaan Welvaart from comment #15)
> To block cast traffic I simply blocked all traffic from the cast-enabled
> device on the PC, since neither the PC nor the TV box acts as a server to
> the other:
>   iptables -m mac -t raw -A PREROUTING --mac-source xx:xx:xx:xx:xx:xx -j DROP
> 
> with xx:xx:xx:xx:xx:xx the MAC address of the USB ethernet adapter I use for
> my Xiaomi Mi Box.
> 
> I tried changing several cast related settings in chromium, but nothing
> helped.
> 
> 
> To debug this crash I think I need debug info, while gcc currently can't
> build chromium with debug info unless it's updated to the next version (gcc
> 11), or the changes outlined in the following patch are applied:
> 
> https://gcc.gnu.org/pipermail/gcc-patches/2020-December/560734.html

[rolf@x570i ~]$ rpm -q chromium-browser-stable
chromium-browser-stable-89.0.4389.114-1.mga8

I updated to testing, which also crashed.  Then, I followed your recipe, best I could, not being adept at iptables.  There are two suspect devices on the lan, an LG TV running WebOS and nVidia shield, as noted in #14.  Steps that seemed to succeed:

1.  Enable firewall in MCC, disabled to solve some LAN problem, unchecking Interactive and Logging, the first not showing up if enabled, the second in an attempt not to have tty's flooded with firewall messages, knock on wood.

2.  $ sudo iptables -m mac -t raw -A PREROUTING --mac-source e8:5b:5b:93:25:d2 -j DROP

3.  $ sudo iptables -m mac -t raw -A PREROUTING --mac-source 48:b0:2d:09:5c:b9 -j DROP
(These two MACS belonging to the devices in question, according to the OpenWRT dhcp table)

4.  $ sudo service iptables restart

Since then the noted updates-testing version has been running and working, AFAICT.

Although I don't use this casting feature from my PC, currently, it does seem cleaner not to have to block it.

Thanks.
Curtis Hildebrand 2021-04-07 19:17:10 CEST

CC: (none) => curtis_mageia

Comment 17 Aurelien Oudelet 2021-04-08 12:12:49 CEST
NO!

You are suggesting user *MUST* use iptables rules tu prevent Chromium crash because of presence in user's network of Smart TV, Google Cast, Google Home, or whatever smart devices.

This is absolutely UN-user-friendly!

Only Version 88.0.4324.150 runs fine on such systems. I will not unplug my Samsung TV (which have a Google Cast built-in), and the Freebox Player (which has an Amazon Alexa interface) when I browse the Net with chromium on my computer. Other family members are able to watch TV. This is a no GO.

So no, please help us fix it.


We are currently in bad situation with Covid19 Lockdown around the world.
Current Firefox ESR is unable to use some WebRTC/screen sharing/videoconference.
Now, if chromium in latest version crashes because of obscur sharing... NO.

We can't be totally un-user-friendly by doing this.
Comment 18 Pascal Terjan 2021-04-08 17:17:15 CEST
The fix seems to be 
https://gitweb.gentoo.org/repo/gentoo.git/plain/www-client/chromium/files/chromium-89-EnumTable-crash.patch

Fedora also added it 2 weeks ago

CC: (none) => pterjan

Comment 19 Aurelian R 2021-04-09 08:06:41 CEST
 The last version of Chromium on Cauldron still crashes when a casting device is active in local network.
 However, more worrying news are coming from google for heavy user of Chromium:
https://hackaday.com/2021/01/26/whats-the-deal-with-chromium-on-linux-google-at-odds-with-package-maintainers/#more-458130
Comment 20 Aurelian R 2021-04-09 08:25:50 CEST
Sorry, for my last comment about Chromium news. It seems it's an old one that got in my news feed now. :(
Christiaan Welvaart 2021-04-09 10:32:26 CEST

URL: (none) => https://bugs.chromium.org/p/chromium/issues/detail?id=1174991

Comment 21 Christiaan Welvaart 2021-04-09 12:01:01 CEST
I tested locally with the patch on 90.0.4430.61. No more crashes and casting works, so assuming it was not fixed upstream after 90.0.4430.51, the patch does indeed fix the problem.
Comment 22 Aurelien Oudelet 2021-04-09 12:03:50 CEST
(In reply to Christiaan Welvaart from comment #21)
> I tested locally with the patch on 90.0.4430.61. No more crashes and casting
> works, so assuming it was not fixed upstream after 90.0.4430.51, the patch
> does indeed fix the problem.

Seems promising!
Comment 23 david Cossé 2021-04-14 11:24:24 CEST
I also have this bug but without having smartTV.
however I have many docker networks.

br-fc21ca8d6635: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 172.18.0.1  netmask 255.255.0.0  broadcast 172.18.255.255
        inet6 fe80::42:6dff:fe9c:cd76  prefixlen 64  scopeid 0x20<link>
        ether 02:42:6d:9c:cd:76  txqueuelen 0  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 170  bytes 73634 (71.9 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

docker0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 172.17.0.1  netmask 255.255.0.0  broadcast 172.17.255.255
        inet6 fe80::42:cdff:feb2:c95b  prefixlen 64  scopeid 0x20<link>
        ether 02:42:cd:b2:c9:5b  txqueuelen 0  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 170  bytes 73634 (71.9 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

enp2s0f0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether b8:88:e3:b4:46:4c  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 16  

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Boucle locale)
        RX packets 51787  bytes 12284546 (11.7 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 51787  bytes 12284546 (11.7 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

veth5c48fc1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet6 fe80::b004:cdff:fe62:b038  prefixlen 64  scopeid 0x20<link>
        ether b2:04:cd:62:b0:38  txqueuelen 0  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 263  bytes 130407 (127.3 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

vethc48dcdc: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet6 fe80::447e:bbff:fe39:fd67  prefixlen 64  scopeid 0x20<link>
        ether 46:7e:bb:39:fd:67  txqueuelen 0  (Ethernet)
        RX packets 20136  bytes 37474284 (35.7 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 21061  bytes 5140528 (4.9 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlp3s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.1.47  netmask 255.255.255.0  broadcast 192.168.1.255
        inet6 fe80::da24:6169:822c:5e17  prefixlen 64  scopeid 0x20<link>
        inet6 2a01:e0a:458:ed40:fdae:86d1:cbe4:a718  prefixlen 64  scopeid 0x0<global>
        ether f4:b7:e2:13:67:f3  txqueuelen 1000  (Ethernet)
        RX packets 100116  bytes 83800116 (79.9 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 85139  bytes 20336264 (19.3 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

CC: (none) => saveurlinux

Comment 24 Aurelien Oudelet 2021-04-14 16:26:09 CEST
Fixed with added patch from Comment 18 in
chromium-browser-89.0.4389.114-2.mga 7/8/9

Closing.

Resolution: (none) => FIXED
Status: NEW => RESOLVED


Note You need to log in before you can comment on or make changes to this bug.