New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 685516 link

Starred by 4 users
Status: WontFix
Owner: ----
Closed: Jan 2018
Cc:
█ zoeclifford@chromium.org
kkaluri@chromium.org
skyos...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Segmentation fault when I click on a webpage in headless mode

Reported by lawn...@gmail.com, Jan 26 2017 
UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.87 Safari/537.36

Steps to reproduce the problem:
1. run `google-chrome-unstable --headless --disable-gpu --remote-debugging-port=9222 https://www.google.com`
2. Open http://localhost:9222 in your browser and click "Google"
3. Click on the search input box

What is the expected behavior?

What went wrong?
Segmentation fault (core dumped)

Did this work before? Yes 57.0.2970.0

Chrome version: 57.0.2987.8  Channel: dev
OS Version: Ubuntu 16.04.1
Flash Version: N/A

Comment 1 by kkaluri@chromium.org, Jan 30 2017

Cc: kkaluri@chromium.org
Labels: hasbisect
Owner: alph@chromium.org
Status: Assigned (was: Unconfirmed)
Able to reproduce this issue on  Ubuntu 14.04 on latest chrome dev  #57.0.2987.13

Bisect Info:
===========
Good build : 57.0.2959.0,  Revision Range- 440307
Bad build  : 57.0.2961.0,  Revision Range- 440662

After executing the (old)bisect script, i got the following CL's between good and bad build versions
============================================
https://chromium.googlesource.com/chromium/src/+log/7dab4a5d9e36d0041c5f4f5101c2816b0b16fee8..b29e220bd93d7ba7d6d7287ae6789aa46a31b096

The suspecting Change Log is :
-----------
https://chromium.googlesource.com/chromium/src/+/8f4f77835fe30ddf1d941904fa8ac6326d612f5e

Review-Url: https://codereview.chromium.org/2593273003

alph@- Could you please look into this issue, if it's related to your change?  if not could you please help us to reassign this issue to the right owner.


Thank You...

Comment 2 by eseckler@chromium.org, Feb 7 2017

Cc: zoeclifford@chromium.org
Labels: Proj-Headless
Do you have a stacktrace for this? It may be related / the same as an error that zoeclifford@ was looking into last week.

Comment 3 by eseckler@chromium.org, Feb 7 2017

Cc: skyos...@chromium.org

Comment 4 by lawn...@gmail.com, Feb 7 2017 

eseckler@:
When I reproduced this in a vanilla Ubuntu install (I originally encountered this running in a Docker container), their crash reporter claimed to have sent something to wherever it sends things. I have no idea how to connect you with those reports.

I am not sure how to gather a stack trace. I read https://www.chromium.org/developers/crash-reports, but AFAICT, I would need to enable Breakpad and build Chrome to get a crash report.

Comment 5 by skyos...@chromium.org, Feb 7 2017 

We're still working in enabling crash reporting in headless mode. My guess this is the same bug as the one Zoe was looking at since it's quite easy to trigger by clicking on things.

Comment 6 by zoeclifford@chromium.org, Feb 23 2017 

Ah, sorry I didn't see this bug earlier, my email forwarding was actually not forwarding.

The bug I saw involved an issue where headless chromium would use the aurax11 clipboard, but hit a DCHECK somewhere (which I thought was because it didn't actually have x11).

Unfortunately I can't reproduce that bug (or this bug) today no matter how I click on things; so I can't say if it's the same issue or not.

Comment 7 by skyos...@chromium.org, May 15 2017

Components: Internals>Headless

Comment 8 by alph@chromium.org, Jan 10 2018

Owner: ----
Status: WontFix (was: Assigned)
Can't repro as on M65.
►

Sign in to add a comment