Bug 1157181 - google-chrome 38.0.2125.104 fails to open any windows with any kernel version after 3.18.0.rc0.git6.1.x86_64
Summary: google-chrome 38.0.2125.104 fails to open any windows with any kernel version...
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: rawhide
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-10-25 20:07 UTC by Peter Trenholme
Modified: 2014-10-29 20:29 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-10-29 20:29:21 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
strace output (214.30 KB, text/plain)
2014-10-25 20:07 UTC, Peter Trenholme
no flags Details

Description Peter Trenholme 2014-10-25 20:07:20 UTC
Created attachment 950697 [details]
strace output

Description of problem:
Google Chrome 38.0.2125.104 fails to open any windows with --replacepkgs

Version-Release number of selected component (if applicable):
Any kernel version after 3.18.0.rc0.git6.1.x86_64

How reproducible:
Every time

Steps to Reproduce:
1.Start google-chrome
2.
3.

Actual results:
No display, no terminal messages, no ...

Expected results:
Chrome browser display

Additional info:
I've attached a (merged) output from a 'strace -Dttffo tmp/strace/google/google-chrome / google-chrome' command. (This was run from a "root" terminal window since the google-sandbox will not run under strace.) I was away from my system for a while, and, when I returned, I terminated the (still hung) strace command with a ^C. Lokking at the tail of the output, you can see the four processes that were still open.)

Note: I suspect that this a kernel issue since it works when I boot with the 3.18.0.rc0.git6.1 kernel, even after several full upgrades of my rawhide system (now using 3.18.0-0.rc1.git2.1.fc22.x86_64) so the only binary difference between the failing and running Google Chrome application is the booted kernel.

I also noticed that, even after terminating the Google Chrome command, the 4377 process (/opt/google/chrome/chrome-sandbox /opt/google/chrome/chrome --type=zygote) is still active.

I suspect that the google-sandbox program is not compatable with a change made after 3.18.0.rc0.git6.1, but I'm not able to do much more than suggest the possibility.

Comment 1 Josh Boyer 2014-10-28 18:26:10 UTC
Please try the 3.18.0-0.rc2.git1.1 kernel that is current building.  There was an upstream RCU issue that was causing hangs for a number of people.

Comment 2 Peter Trenholme 2014-10-29 20:29:21 UTC
Fixed with rc2.git1.1. Thanks.


Note You need to log in before you can comment on or make changes to this bug.