Chrome cauisng PC screen to Freeze |
||
Issue descriptionRecently started the process of replacing older PC's with HP All-In-One machines. These machines are in a domain enviroment. They are running Windows 7 Pro. The issue is that Chrome will randomally freeze the screen. Stil have mouse movemnet, but can't perform changes. After some time the system will return to normal, expet for the machine time being off. I have tested this with other browsers and the issue isn't there. Only Chrome. I have tried many different version of Chrome, but that hasn't changed anything. I have uninstalled Chrome, delted the local and domain user. Removed Goolge from C:\"user"\appdata\local, and C:\Programsx86. None of this have changed the issue. Chrome Log: [4456:4396:0407/101054.795:ERROR:child_thread_impl.cc(762)] Request for unknown Channel-associated interface: ui::mojom::GpuMain [3804:4932:0407/101054.815:WARNING:external_registry_loader_win.cc(211)] Error observing HKLM. [3804:2328:0407/101157.032:ERROR:backend_impl.cc(1033)] Critical error found -8 [3804:2328:0407/101157.049:WARNING:storage_block-inl.h(131)] Failed data load. [3804:2328:0407/101157.050:WARNING:storage_block-inl.h(131)] Failed data load. [3804:2328:0407/101157.050:WARNING:storage_block-inl.h(131)] Failed data load. [3804:2328:0407/101157.050:WARNING:storage_block-inl.h(131)] Failed data load. [3804:4932:0407/101706.387:INFO:CONSOLE(6)] "SW registered", source: https://www.google.com/_/chrome/newtab?espv=2&ie=UTF-8 (6) [3804:4932:0407/101712.752:INFO:CONSOLE(2)] "JQMIGRATE: Migrate is installed, version 1.4.1", source: http://www.nsider.com/wp-includes/js/jquery/jquery-migrate.min.js?ver=1.4.1 (2) [3804:4932:0407/101723.040:INFO:CONSOLE(210)] "Google Maps API warning: NoApiKeys https://developers.google.com/maps/documentation/javascript/error-messages#no-api-keys", source: https://maps-api-ssl.google.com/maps-api-v3/api/js/28/8/util.js (210) [3804:4932:0407/101723.040:INFO:CONSOLE(210)] "Google Maps API warning: SensorNotRequired https://developers.google.com/maps/documentation/javascript/error-messages#sensor-not-required", source: https://maps-api-ssl.google.com/maps-api-v3/api/js/28/8/util.js (210) Similar thread: http://stackoverflow.com/questions/43266033/python-selenium-chromedriver-error-on-new-browser-object Original discussion here: https://productforums.google.com/forum/#!topic/chrome-admins/NbfqMzNzTvE
,
Apr 10 2017
I think that's unlikely. Is it possible to get a trace report for the session when the freeze happens?
,
Apr 11 2017
Sadrul please provide instructions for the user how to do this I guess it is a combination of these command line flags but you might have a better information? --trace-startup --trace-startup-duration=XXX --trace-to-file --trace-to-filename=<filename>
,
Apr 11 2017
Those command line flags should work, yes. But the easier way would be to use the UI in 'chrome:tracing'. Hit record on 'chrome:tracing' page before the freeze happens. Then hit 'stop' after the freeze ends. Then 'save' will save the trace to a json file. Additional instructions: https://www.chromium.org/developers/how-tos/trace-event-profiling-tool/recording-tracing-runs#TOC-Capture-a-trace-on-Chrome-desktop Looking back at the logs: [3804:4932:0407/101054.815:WARNING:external_registry_loader_win.cc(211)] Error observing HKLM. [3804:2328:0407/101157.032:ERROR:backend_impl.cc(1033)] Critical error found -8 I think there's a gap of ~100 seconds between these to logs? Could it be related to either of these logs?
,
Apr 12 2017
The HKLM error is not critical and is pretty common so I don't think it reveals anything in regard to this issue.
,
Apr 13 2017
sadrul you should have gotten a shared drive file on your email with the trace. :)
,
Apr 24 2017
Hello sadrul, any info on this issue?
,
Apr 28 2017
I received the email, but I was unable to load the sent tracing data in chrome. pastarmovj@ were you able to?
,
Apr 28 2017
I tried now and saw the problem but I think the issue is it's sheer size. I think the code is not made to handle such large files. Can you try to slice manually the last say 10% and see if this loads?
,
May 5 2017
An alternate option for investigating would be to grab an ETW trace, which I could then analyze. I've created a tool to make this as easy as possible and I've documented the process here: https://randomascii.wordpress.com/2015/09/01/xperf-basics-recording-a-trace-the-ultimate-easy-way/ The basic steps should work fine - I doubt the Chrome specific steps will be needed. Recording ETW traces requires the ability to install software and then run it as admin. If that's okay then the process should be pretty straightforward. If you can share the file with brucedawson @ chromium.org then I will look at it. Let me know if you have any questions. It is not guaranteed that this will identify the cause but it is highly likely.
,
Nov 15
I'm assuming this is no longer an issue. If it is, please re-open with some additional feedback. |
||
►
Sign in to add a comment |
||
Comment 1 by yzshen@chromium.org
, Apr 10 2017