Issue metadata
Sign in to add a comment
|
Chrome crashes on keypress when using Gtk3 and Wayland
Reported by
mikhail....@gmail.com,
Mar 18 2017
|
||||||||||||||||||
Issue description
UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3018.3 Safari/537.36 OPR/45.0.2531.0 (Edition developer)
Steps to reproduce the problem:
1. Launch browser
2. Start input url in address bar
3.
What is the expected behavior?
What went wrong?
[mikhail@localhost ~]$ google-chrome
[19788:19788:0318/115731.839683:ERROR:display_info_provider_aura.cc(31)] Not implemented reached in virtual void extensions::DisplayInfoProviderAura::UpdateDisplayUnitInfoForPlatform(const display::Display &, extensions::api::system_display::DisplayUnitInfo *)
[1,3187345088:06:57:33.111262] Native Client module will be loaded at base address 0x00007c3000000000
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 82 0 82 0 0 427 0 --:--:-- --:--:-- --:--:-- 496
--2017-03-18 11:57:58-- https://clients2.google.com/cr/report
Resolving clients2.google.com (clients2.google.com)... 2a00:1450:4010:c06::66, 173.194.122.206, 173.194.122.194, ...
Connecting to clients2.google.com (clients2.google.com)|2a00:1450:4010:c06::66|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: ‘/dev/fd/4’
0K
Crash dump id: 3edde1d660000000
1,70M=0s
2017-03-18 11:58:00 (1,70 MB/s) - ‘/dev/fd/4’ saved [16]
Segmentation fault (core dumped)
[mikhail@localhost ~]$ google-chrome
[20515:20549:0318/115806.740267:ERROR:cache_storage_cache.cc(1454)] Cache size: 1116932 does not match size from index: 1119067
[20515:20549:0318/115806.921080:ERROR:cache_storage_cache.cc(1454)] Cache size: 1117078 does not match size from index: 1116932
[20515:20549:0318/115807.052371:ERROR:cache_storage_cache.cc(1454)] Cache size: 1117248 does not match size from index: 1117078
[20515:20549:0318/115807.154872:ERROR:cache_storage_cache.cc(1454)] Cache size: 1117579 does not match size from index: 1117248
[20515:20515:0318/115807.231782:ERROR:display_info_provider_aura.cc(31)] Not implemented reached in virtual void extensions::DisplayInfoProviderAura::UpdateDisplayUnitInfoForPlatform(const display::Display &, extensions::api::system_display::DisplayUnitInfo *)
[20515:20549:0318/115807.526036:ERROR:cache_storage_cache.cc(1454)] Cache size: 1117913 does not match size from index: 1117579
[20515:20549:0318/115808.038227:ERROR:cache_storage_cache.cc(1454)] Cache size: 1118339 does not match size from index: 1117913
[20515:20549:0318/115808.060721:ERROR:cache_storage_cache.cc(1454)] Cache size: 1118572 does not match size from index: 1118339
[1,2778150592:06:58:08.618561] Native Client module will be loaded at base address 0x00004b7e00000000
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 82 0 82 0 0 389 0 --:--:-- --:--:-- --:--:-- 453
[20515:20549:0318/115811.176021:ERROR:cache_storage_cache.cc(1454)] Cache size: 1118779 does not match size from index: 1118572
--2017-03-18 11:58:23-- https://clients2.google.com/cr/report
Resolving clients2.google.com (clients2.google.com)... 2a00:1450:4010:c06::66, 173.194.122.196, 173.194.122.192, ...
Connecting to clients2.google.com (clients2.google.com)|2a00:1450:4010:c06::66|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: ‘/dev/fd/4’
0K
Crash dump id: c5409b9480000000
514K=0s
Segmentation fault (core dumped)
[mikhail@localhost ~]$ google-chrome
[21245:21245:0318/115835.396112:ERROR:display_info_provider_aura.cc(31)] Not implemented reached in virtual void extensions::DisplayInfoProviderAura::UpdateDisplayUnitInfoForPlatform(const display::Display &, extensions::api::system_display::DisplayUnitInfo *)
[1,261498560:06:58:36.456333] Native Client module will be loaded at base address 0x0000092d00000000
--2017-03-18 11:58:36-- https://clients2.google.com/cr/report
Resolving clients2.google.com (clients2.google.com)... 2a00:1450:4010:c06::66, 173.194.122.201, 173.194.122.206, ...
Connecting to clients2.google.com (clients2.google.com)|2a00:1450:4010:c06::66|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: ‘/dev/fd/4’
0K
Crash dump id: a3449b9480000000
1,99M=0s
Segmentation fault (core dumped)
Crashed report ID: a3449b9480000000
How much crashed? Whole browser
Is it a problem with a plugin? N/A
Did this work before? N/A
Chrome version: 59.0.3043.0 Channel: dev
OS Version: Fedora 25
Flash Version:
,
Mar 18 2017
Fedora 25 x86_64
,
Mar 18 2017
> I'm looking at your stack trace and the crash appears to be in gdk3. # dnf install gtk3-debuginfo Last metadata expiration check: 3:23:16 ago on Sat Mar 18 09:05:23 2017. Dependencies resolved. =================================================================================================================================================================================================================== Package Arch Version Repository Size =================================================================================================================================================================================================================== Installing: gtk3-debuginfo x86_64 3.22.10-1.fc25 updates-debuginfo 13 M Transaction Summary =================================================================================================================================================================================================================== Install 1 Package Total download size: 13 M Installed size: 76 M Is this ok [y/N]: y Downloading Packages: gtk3-debuginfo-3.22.10-1.fc25.x86_64.rpm 1.6 MB/s | 13 MB 00:08 ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Total 1.4 MB/s | 13 MB 00:09 Running transaction check Transaction check succeeded. Running transaction test Transaction test succeeded. Running transaction Installing : gtk3-debuginfo-3.22.10-1.fc25.x86_64 1/1 Verifying : gtk3-debuginfo-3.22.10-1.fc25.x86_64 1/1 Installed: gtk3-debuginfo.x86_64 3.22.10-1.fc25 Crash dump id: 30f8c5d660000000
,
Mar 18 2017
> 'objdump -d' please? $ objdump -d objdump: 'a.out': No such file
,
Mar 18 2017
The package you installed (gtk3-debuginfo-3.22.10-1.fc25.x86_64) should have added some file like libgdk-3.so.0.2200.10 Probably it will be /usr/lib/debug/usr/lib/x86_64-linux-gnu/libgdk-3.so.0.2200.10 Run "objdump -d <file>"
,
Mar 18 2017
FYI right path for .so file: objdump -d /usr/lib64/libgtk-3.so.0.2200.10
,
Mar 18 2017
Thanks but that objdump is for gtk not gdk
,
Mar 18 2017
Thanks for assisting with the debugging. I believe I know what the issue is now, and we should have a fix out by next week's dev release :)
,
Mar 20 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/5d073abb6966b9c2d2ad1033c8a0e3396072c0f3 commit 5d073abb6966b9c2d2ad1033c8a0e3396072c0f3 Author: thomasanderson <thomasanderson@google.com> Date: Mon Mar 20 22:58:40 2017 Gtk3: Whitelist X11 backend Gtk can only have one window server backend active at a time. On systems running Wayland (like Fedora 25), Gtk will prefer the Wayland backend over the X11 one. This violates the assumption in libgtkui about th euse of X11, and will eg. cause a crash on keypress in X11InputMethodContextImplGtk. The solution is to forbid Wayland using gdk_set_allowed_backends("x11") prior to gtk_init(). BUG= 702876 R=erg@chromium.org Review-Url: https://codereview.chromium.org/2762723003 Cr-Commit-Position: refs/heads/master@{#458218} [modify] https://crrev.com/5d073abb6966b9c2d2ad1033c8a0e3396072c0f3/chrome/browser/ui/libgtkui/gtk_ui.cc [modify] https://crrev.com/5d073abb6966b9c2d2ad1033c8a0e3396072c0f3/chrome/browser/ui/libgtkui/gtk_util.cc [modify] https://crrev.com/5d073abb6966b9c2d2ad1033c8a0e3396072c0f3/chrome/browser/ui/libgtkui/gtk_util.h
,
Mar 21 2017
,
Mar 21 2017
Question: chrome will not use Wayland?
,
Mar 21 2017
Chromium currently relies on XWayland, but there is an effort to add native Wayland support. There are currently 2 engineers (not at Google) working on this, but it is still a ways off.
,
Mar 22 2017
You mean project ozone-wayland? I see that it is abandoned, there are no fresh commits. It would be nice if Google took it under their care.
,
Mar 22 2017
Not ozone-wayland. See eg. https://crbug.com/666958 |
|||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||
Comment 1 by thomasanderson@chromium.org
, Mar 18 2017