New issue
Advanced search Search tips

Issue 759493 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Aug 2017
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Google Chrome 60.0.3112.113 freezes right after the first click

Reported by gustavka...@gmail.com, Aug 28 2017

Issue description

UserAgent: Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:55.0) Gecko/20100101 Firefox/55.0

Steps to reproduce the problem:
1. Open Google Chrome version 60.0.3112.113 from the terminal on Fedora Core Linux 26
2. When the screen opens, try to click on the address bar to enter a URL

What is the expected behavior?
That I can use the browser

What went wrong?
From the terminal window I have the following output:

[30943:30943:0828/112050.045686:ERROR:background_mode_manager_aura.cc(13)] Not implemented reached in virtual void BackgroundModeManager::EnableLaunchOnStartup(bool)
[31062:31062:0828/112050.160505:ERROR:sandbox_linux.cc(344)] InitializeSandbox() called with multiple threads in process gpu-process.
[30943:30943:0828/112051.147831:ERROR:CONSOLE(1)] "Uncaught SecurityError: Blocked a frame with origin "https://clients5.google.com" from accessing a frame with origin "https://www.google.dk". Protocols, domains, and ports must match.", source:  (1)
[30943:30943:0828/112054.734463:ERROR:CONSOLE(1)] "Uncaught SecurityError: Blocked a frame with origin "https://clients5.google.com" from accessing a frame with origin "https://www.google.dk". Protocols, domains, and ports must match.", source:  (1)

Crashed report ID: No

How much crashed? Whole browser

Is it a problem with a plugin? N/A 

Did this work before? Yes Version 60.0.3112.101

Chrome version: Google Chrome 60.0.3112.113  Channel: stable
OS Version: Linux 4.12.8-300.fc26.x86_64 #1 SMP Thu Aug 17 15:30:20 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
Flash Version: Shockwave Flash 26.0 r0

I cleared the ~/.config/google-chome and ~/.cache/google-chrome folders
 
okay - I just tried downgrading to a previous version - that was no good either, so this must be caused by something else.

So I restarted my system, and now it works.
 - I think it was caused by the machine having been a sleep.

This issue can be closed

Status: WontFix (was: Unconfirmed)

Sign in to add a comment