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

Issue 764222 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Last visit 29 days ago
Closed: Nov 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 3
Type: Bug



Sign in to add a comment

Canary - Setting download behavior creates seg fault when not in headless

Reported by peter.r...@renvest.de, Sep 12 2017

Issue description

Chrome Version: 63.0.3212.0 (Offizieller Build) canary (64-Bit)
OS Version: OS X 10.12.6

What steps will reproduce the problem?
1. When I start Chrome headless /Applications/Google\ Chrome\ Canary.app/Contents/MacOS/Google\ Chrome\ Canary --remote-debugging-port=9222 --disable-gpu --headless and set the download behavior to allow everything works as expected

2. However when for debugging purpose I omit --headless and --disable-gpu but my script still sets the download behavior Chrome crashes with a seg fault




 
Cc: keerthan...@techmahindra.com
Components: Internals>Headless
Labels: Proj-Headless Needs-Triage-M63 Triaged-ET
Status: Untriaged (was: Unconfirmed)
Appropriate component and label is added for further triage and marking it as untriaged.
Cc: alexclarke@chromium.org
Owner: dvallet@chromium.org
David could you take a look please?
Sorry for the late reply (I was OOO for most of the last few weeks)

I can't reproduce the issue. 
One thing to note is that non headless chrome would attempt to load the default user profile defined in --user-data-dir flag, and perhaps that could be conflicting with the download behavior command (this can happen with previous profiles since the download manager behavior changed a bit)

Try setting a new user data dir and checking if it works (e.g., using --user-data-dir=/tmp/user1/)

Thanks for the feedback, seems fixed with one of the recent bulds, at least I cannot reproduce as well.
Status: WontFix (was: Untriaged)

Sign in to add a comment