Project

General

Profile

Bug #9808

edge: chromium 71.0.3578 is a mess!

Added by Steffen Nurpmeso 4 months ago. Updated about 2 months ago.

Status:
Closed
Priority:
High
Assignee:
Category:
Aports
Target version:
Start date:
12/28/2018
Due date:
% Done:

100%

Estimated time:
Affected versions:
Security IDs:

Description

After the last update of chromium it has become extremely slow, and i see myriads of error messages, some of which are new; the bus and libGL.. errors are "normal" (stripped):

[30044:30061:1228/153401.207867:ERROR:bus.cc(396)] Failed to connect to the bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
[30044:30044:1228/153401.271064:ERROR:browser_dm_token_storage_linux.cc(93)] Error: /etc/machine-id contains 0 characters (32 were expected).
..
libva error: va_getDriverName() failed with unknown libva error,driver_name=(null)
[30077:30077:1228/153401.473308:ERROR:vaapi_wrapper.cc(324)] vaInitialize failed: unknown libva error
libGL error: unable to load driver: swrast_dri.so
libGL error: failed to load driver: swrast
Received signal 11 SEGV_MAPERR 00000000000c
...
[end of stack trace]
Calling _exit(1). Core file will not be generated.
libva error: va_getDriverName() failed with unknown libva error,driver_name=(null)
[30104:30104:1228/153402.650192:ERROR:vaapi_wrapper.cc(324)] vaInitialize failed: unknown libva error
[30104:30104:1228/153402.658632:ERROR:gl_implementation.cc(281)] Failed to load /usr/lib/chromium/swiftshader/libGLESv2.so: Error loading shared library /usr/lib/chromium/swiftshader/libGLESv2.so: No such file or directory
[30104:30104:1228/153402.709976:ERROR:viz_main_impl.cc(184)] Exiting GPU process due to errors during initialization
[30044:30054:1228/153402.734271:ERROR:browser_gpu_channel_host_factory.cc(139)] Failed to launch GPU process.
[30044:30044:1228/153402.754279:ERROR:gpu_process_transport_factory.cc(967)] Lost UI shared context.
...

Associated revisions

Revision 01e08233 (diff)
Added by Natanael Copa about 2 months ago

community/chromium: upgrade to 72.0.3626.109 and fix deadlock

ref #9808

Upstream bug report: https://bugs.chromium.org/p/v8/issues/detail?id=8881

Revision d792e5d8 (diff)
Added by Natanael Copa about 2 months ago

community/chromium: upgrade to 72.0.3626.109 and fix deadlock

fixes #9808

Upstream bug report: https://bugs.chromium.org/p/v8/issues/detail?id=8881

(cherry picked from commit 01e082330dad92dec25b85358b790686fd54ce68)

History

#1 Updated by David Rodríguez 4 months ago

I don't know if it's related, but some CI builds of mine broke after chromium and chromium-chromedriver from edge were upgraded. Is there a way I can pin to chromium 68, also to confirm that the upgrade caused the issue?

#2 Updated by Natanael Copa 4 months ago

  • Target version changed from 3.8.3 to 3.9.0

3.8 should not be affected.

#3 Updated by Natanael Copa 4 months ago

  • Affected versions 3.9.0 added
  • Affected versions deleted (3.8.2)

#4 Updated by Natanael Copa 4 months ago

David Rodríguez wrote:

I don't know if it's related, but some CI builds of mine broke after chromium and chromium-chromedriver from edge were upgraded. Is there a way I can pin to chromium 68, also to confirm that the upgrade caused the issue?

Use alpine 3.8 instead of edge. apk add 'chromium<69'.

#5 Updated by Natanael Copa 4 months ago

I can also add that on my workstation, while I don't see the libva related errors, nor suffer from performance loss, some tabs hangs occasionally and I am not sure why.

#6 Updated by Natanael Copa 4 months ago

what architecture is it?

#7 Updated by Rep H 4 months ago

I have the same problem.
Chromium 71 becomes unresponsive (mostly on Google pages like Gmail) and hangs.
Downgrading to Chromium 68 while keeping the rest of the system on Edge didn't work (Chromium 68 would segfault). I had to downgrade linux-vanilla too.
For everyone who has this issue, here's how I did it:
Added this to the end of /etc/apk/repositories:
@3.8community http://dl-cdn.alpinelinux.org/alpine/v3.8/community/
@3.8main http://dl-cdn.alpinelinux.org/alpine/v3.8/main/
Ran:
sudo apk del chromium linux-vanilla
sudo apk update
sudo apk add
Rebooted to reload kernel.

Now I'm back to Chromium 68 and it works.
But there's something else that worried me on Chromium 71...
When signing in to Gmail, Youtube or any other Google service, Chromium now automatically signs you into a Google session in the browser (check the icon on the top right corner).
Apparently there was a flag to disable this ( https://news.ycombinator.com/item?id=17942723 ) but it doesn't fully do the job ( https://news.ycombinator.com/item?id=17943524 ).

This is just too much for me, the "integration" (spying? tracking?) between Chromium and Google is too much.

#8 Updated by Steffen Nurpmeso 4 months ago

I am x86_64.
Total freezes i see too, occasionally. (That is, little boxes show up that say the page is not responding or such, whether i want to exit them.)

#9 Updated by Natanael Copa 4 months ago

I need help debugging this. Things that I have tested so far, but that does not seem to make any difference:

- unset CFLAGS/CXXFLAGS
- switch from gold linker to ld.
- enforce -fno-delete-null-pointer-checks

It seems that running chromium with --no-sandbox makes a difference though, so I suspect it is related the sandbox.

It is possible that this is related too (but I'm not convinced its the same issue): https://bugs.chromium.org/p/chromium/issues/detail?id=912176

#10 Updated by Natanael Copa 4 months ago

I managed to get a crash with chromium-browser --debug --single-process

[3571:3647:0101/123825.161597:ERROR:object_proxy.cc(621)] Failed to call method: org.freedesktop.NetworkManager.GetDevices: object_path= /org/freedesktop/NetworkManager: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.NetworkManager was not provided by any .service files
[3571:3571:0101/123901.604922:ERROR:gaia_auth_fetcher.cc(71)] Missing ID token on refresh token fetch response.
[3571:3571:0101/125956.309820:ERROR:CONSOLE(1)] "Not allowed to load local resource: chrome-search://local-ntp/theme.css", source: https://www.google.no/_/chrome/newtab?ie=UTF-8 (1)
[3571:3647:0101/125956.874917:ERROR:object_proxy.cc(621)] Failed to call method: org.freedesktop.NetworkManager.GetDevices: object_path= /org/freedesktop/NetworkManager: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.NetworkManager was not provided by any .service files
[3571:3956:0101/130110.536094:FATAL:wtf.cc(68)] Check failed: !g_initialized. 
Received signal 6
  r8: 0000000000000030  r9: 00007fa95d6b814c r10: 0000000000000008 r11: 0000000000000246
 r12: 00007fa94b2f1548 r13: 000000000000004e r14: 00007fa94b2f1568 r15: 00007fa94b2f1d18
  di: 0000000000000002  si: 00007fa94b2f1420  bp: 00007fa94b2f1420  bx: 0000000000000006
  dx: 0000000000000000  ax: 0000000000000000  cx: 00007fa95d66ef6f  sp: 00007fa94b2f1408
  ip: 00007fa95d66ef6f efl: 0000000000000246 cgf: 002b000000000033 erf: 0000000000000000
 trp: 0000000000000000 msk: 0000000000000000 cr2: 0000000000000000
[end of stack trace]
Calling _exit(1). Core file will not be generated.

#11 Updated by David Rodríguez 4 months ago

Natanael Copa wrote:

David Rodríguez wrote:

I don't know if it's related, but some CI builds of mine broke after chromium and chromium-chromedriver from edge were upgraded. Is there a way I can pin to chromium 68, also to confirm that the upgrade caused the issue?

Use alpine 3.8 instead of edge. apk add 'chromium<69'.

Indeed, I think I had upgraded it because at some point 68 was only available on edge. Using 3.8 works, thanks a lot!

#12 Updated by Steffen Nurpmeso 4 months ago

--no-sandbox is interesting since it is an "unknown option", nonetheless the GUI warns on "reduced security". All the options you mentioned do not seem to make a difference. I am only wondering that you seem to have problems to reproduce the SEGVs, they happen permanently. :)
Hopefully this will vanish with a new chromium release..
I could post my APK world, if you want to see that?

#13 Updated by Natanael Copa 3 months ago

  • Target version changed from 3.9.0 to 3.9.1

#14 Updated by Natanael Copa about 2 months ago

  • % Done changed from 0 to 80

I think I finally found a solution for the deadlock.

Upstream report: https://bugs.chromium.org/p/v8/issues/detail?id=8881

#15 Updated by Steffen Nurpmeso about 2 months ago

Impressive sleuthing!
Thanks for ending this, Ew,snap! (I look forward to tomorrows update.)

#16 Updated by Natanael Copa about 2 months ago

  • Status changed from New to Resolved
  • % Done changed from 80 to 100

#17 Updated by Natanael Copa about 2 months ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF