FS#49842 - [chromium] browser process hangs when the 'view site information' on the address bar is clicked
Attached to Project:
Arch Linux
Opened by Alif (alive4ever) - Saturday, 25 June 2016, 13:32 GMT
Last edited by Doug Newgard (Scimmia) - Sunday, 26 June 2016, 14:42 GMT
Opened by Alif (alive4ever) - Saturday, 25 June 2016, 13:32 GMT
Last edited by Doug Newgard (Scimmia) - Sunday, 26 June 2016, 14:42 GMT
|
Details
Description:
When any webpage is loaded, clicking the 'view site information' on the address bar makes the browser hangs , i.e. not responding to any input and not refreshing the display. Additional info: * chromium 51.0.2704.103-1 * under plasma-desktop 5.6.5-1 X session (x86_64) Steps to reproduce: Navigate to any webpage, for example 'https://www.archlinux.org' Click on the green padlock button on the address bar to view site information, such as what is allowed and what is blocked. The browser process hangs afterwards. This also happens with plain http sites. To recover from the hang state, the following command is needed: 'pkill -TERM chromium'. |
This task depends upon
I've also tried starting chromium in a clean state, by moving the config directory ~/.config/chromium to ~/.config/chromium.orig
Let's see if anybody have the same issue.
Jun 26 10:20:13 alive-pc plasmashell[2094]: trying to show an empty dialog
Jun 26 10:20:22 alive-pc kwin_x11[2069]: QXcbConnection: XCB error: 3 (BadWindow), sequence: 19626, resource id: 16777216, major code: 18 (ChangeProperty), minor code: 0
Jun 26 10:20:22 alive-pc kwin_x11[2069]: QXcbConnection: XCB error: 3 (BadWindow), sequence: 19630, resource id: 16777217, major code: 18 (ChangeProperty), minor code: 0
Jun 26 10:20:22 alive-pc plasmashell[2094]: no winId: probably startup task
Jun 26 10:20:39 alive-pc plasmashell[2094]: QXcbConnection: XCB error: 2 (BadValue), sequence: 30249, resource id: 4194310, major code: 142 (Unknown), minor code: 3
Jun 26 10:20:39 alive-pc plasmashell[2094]: QXcbConnection: XCB error: 2 (BadValue), sequence: 30270, resource id: 94371908, major code: 142 (Unknown), minor code: 3
Jun 26 10:22:06 alive-pc kwin_x11[2069]: QXcbConnection: XCB error: 3 (BadWindow), sequence: 14890, resource id: 27339161, major code: 20 (GetProperty), minor code: 0
[9135:9135:0626/102843:ERROR:zygote_communication_linux.cc(392)] Failed to send GetTerminationStatus message to zygote
[9135:9135:0626/102843:ERROR:zygote_communication_linux.cc(392)] Failed to send GetTerminationStatus message to zygote
[9135:9135:0626/102843:ERROR:zygote_communication_linux.cc(392)] Failed to send GetTerminationStatus message to zygote
[9135:9135:0626/102843:ERROR:child_process_launcher.cc(505)] Failed to launch child process
Another log
[9871:10108:0626/103314:ERROR:get_updates_processor.cc(250)] PostClientToServerMessage() failed during GetUpdates
https://chromium.googlesource.com/chromium/src/+/51.0.2704.103/content/browser/zygote_host/zygote_communication_linux.cc
fvwm][GetWindowSizeHints]: <<WARNING>> reason: 2: The hints have been ignored because the window's current size would have become invalid. The new hints will become active when the window generates the next ConfigureRequest.
[fvwm][GetWindowSizeHints]: <<WARNING>> reason: 4: The hints have been ignored because the window's current size would have become invalid. The new hints will become active when the window generates the next ConfigureRequest.
[fvwm][GetWindowSizeHints]: <<WARNING>> reason: 2: The hints have been ignored because the window's current size would have become invalid. The new hints will become active when the window generates the next ConfigureRequest.
[fvwm][GetWindowSizeHints]: <<WARNING>> reason: 4: The hints have been ignored because the window's current size would have become invalid. The new hints will become active when the window generates the next ConfigureRequest.
I switched to KDE after restart and the browser hangs problem is disappeared.