Issue metadata
Sign in to add a comment
|
Hardware acceleration became unavailable
Reported by
marek.se...@gmail.com,
Dec 1 2017
|
||||||||||||||||||||||
Issue description
UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3278.0 Safari/537.36
Steps to reproduce the problem:
1. Linux google-chrome-unstable (64.0.3278.0-1)
2. chrome://gpu
3. observe "Software only, hardware acceleration unavailable"
What is the expected behavior?
Hardware acceleration is enabled, chromium (version 64.0.3282.0 (Developer Build) custom (64-bit)) works correctly.
What went wrong?
1) chrome://gpu shows many lines of "GpuProcessHostUIShim: The GPU process crashed!"
2) override of #ignore-gpu-blacklist chrome://flags, and disable/enable hardware acceleration in chrome://settings does not resolve the issue
3) .xsession-errors shows
117 [14762:14799:1201/071556.909248:ERROR:browser_gpu_channel_host_factory.cc(120)] Failed to launch GPU process.
118 [14762:14762:1201/071556.911270:ERROR:gpu_process_transport_factory.cc(1008)] Lost UI shared context.
119 [46:122:1201/071556.922428:ERROR:adm_helpers.cc(73)] Failed to query stereo recording.
120 [14762:14792:1201/071557.770858:ERROR:form_field_data.cc(364)] Unknown FormFieldData pickle version 0
121 [14762:14792:1201/071557.776059:ERROR:form_field_data.cc(364)] Unknown FormFieldData pickle version 0
122 [14762:14792:1201/071557.776127:ERROR:form_field_data.cc(364)] Unknown FormFieldData pickle version 0
123 [14762:14792:1201/071557.778862:ERROR:form_field_data.cc(364)] Unknown FormFieldData pickle version 0
124 [14762:14792:1201/071605.786465:ERROR:form_field_data.cc(364)] Unknown FormFieldData pickle version 0
125 [14762:14792:1201/071605.798510:ERROR:form_field_data.cc(364)] Unknown FormFieldData pickle version 0
126 [14762:14792:1201/071605.811454:ERROR:form_field_data.cc(364)] Unknown FormFieldData pickle version 0
127 [14762:14792:1201/071605.814528:ERROR:form_field_data.cc(364)] Unknown FormFieldData pickle version 0
Did this work before? Yes 64.0.3269.3 (most probably, by listing https://chromereleases.googleblog.com/ )
Chrome version: 64.0.3278.0 Channel: dev
OS Version: 4.13.0-0.bpo.1-amd64 (Debian 9.1)
Flash Version:
,
Dec 4 2017
Tested this issue on Ubuntu 14.04 using the chrome reported version #64.0.3278.0 1.Launched google-chrome-unstable (64.0.3278.0-1) 2.Navigated to chrome://gpu and didn't observed any chrome://gpu shows many lines of "GpuProcessHostUIShim: The GPU process crashed!"/override of #ignore-gpu-blacklist chrome://flags, and .xsession-errors Please find the attached html.. @Reporter :Could you please recheck the issue with a fresh installation of chrome & without any extensions. Thanks!
,
Dec 4 2017
,
Dec 4 2017
@rkalavakuntla@chromium.org: I've just tried 1) mv .config/google-chrome-unstable .config/oldchrome 2) google-chrome-unstable # (without flags) 3) see gpu.html and attached screenshot I've also restored the user configuration for google-chrome-unstable, and see gpu_live.html that documents current state Also in console output both launches resulted in "Failed to launch GPU process" Clean profile: [15554:15624:1204/122153.278995:ERROR:browser_gpu_channel_host_factory.cc(120)] Failed to launch GPU process. [15554:15554:1204/122153.279150:ERROR:gpu_process_transport_factory.cc(1008)] Lost UI shared context. [15554:15624:1204/122156.492291:ERROR:service_manager.cc(158)] Connection InterfaceProviderSpec prevented service: content_renderer from binding interface: blink::mojom::ReportingServiceProxy exposed by: content_browser Original profile: [16885:16922:1204/122248.204166:ERROR:service_manager.cc(158)] Connection InterfaceProviderSpec prevented service: content_renderer from binding interface: blink::mojom::ReportingServiceProxy exposed by: content_browser [16885:16922:1204/122249.424906:ERROR:browser_gpu_channel_host_factory.cc(120)] Failed to launch GPU process. [16885:16885:1204/122249.425129:ERROR:gpu_process_transport_factory.cc(1008)] Lost UI shared context. [40:120:1204/122249.425281:ERROR:adm_helpers.cc(73)] Failed to query stereo recording. notes: 1) trap int3 in dmesg can be seen for both launches 2) without flags, the browser behaves very badly, with flags, the rendering is at least bit usable (--enable-native-gpu-memory-buffers --enable-zero-copy --cast-initial-screen-width --enable-gpu-rasterization --enable-accelerated-2d-canvas --enable-accelerated-vpx-decode) 3) in the meantime i'm using google-chrome-beta(63.0.3239.70-1) which works correctly and is pleasant as always 4) in ".config/google-chrome-unstable/Crashpad/completed" there is a lot of files, maybe those might help you? Or their names (uuids) ? 5) I don't use Ubuntu, but Debian 9.1, with i3wm as WM, and all usually required vdpau/va/intel drivers, drms, configs are in place (as i already said, beta, stable and clean chromium builds work correctly)
,
Dec 4 2017
Thank you for providing more feedback. Adding requester "rkalavakuntla@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Dec 12 2017
Ok, this regression bug has been fixed in "Version 64.0.3282.14 (Official Build) dev (64-bit)", see the attached screenshots Could you please identify the cause and provide tests, so it won't happen again?
,
Dec 28 2017
Unable to reproduce this issue on reported version 64.0.3278.0 on Ubuntu 14.04. As ET Team doesn't have debian 9 to check this issue ,forwarding to Inhouse for further inputs on this. Thanks!
,
Jan 30 2018
@marek: As per comment #6 can we close this issue. Could you please confirm. Thank You!
,
Jan 31 2018
I guess so, if you found out what the problem was and implemented test-case, it should be ready to close. Since version referenced in comment #6 this issue did not occcur on -dev channel (currently 65.0.3325.18 (Official Build) dev (64-bit))
,
Sep 13
Archiving old bugs that haven't been actively assigned in over 180 days. If you feel this issue should still be addressed, feel free to reopen it or to file a new issue. Thanks! |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by marek.se...@gmail.com
, Dec 1 2017