New issue
Advanced search Search tips

Issue 736763 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Jun 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Chrome Canary 61 crashes on launch with remote-debugging-port param

Reported by jonp...@gmail.com, Jun 26 2017

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3141.0 Safari/537.36

Steps to reproduce the problem:
1. Close Chrome
2. Set Chrome shortcut launch parameters to include --remote-debugging-port=9222
3. Attempt to launch
4. Process starts but never shows a window
5. Process closes
6. Remove parameter
7. Launch Chrome
8. Report bug

What is the expected behavior?
Chrome should launch with parameters

What went wrong?
Chrome crashes on startup

Crashed report ID: 263b207d-9f2b-4b4a-8444-b84926bceb23

How much crashed? Whole browser

Is it a problem with a plugin? No 

Did this work before? Yes 

Chrome version: 61.0.3141.0  Channel: canary
OS Version: 10.0
Flash Version: 

This started happening after the most recent Canary update. I didn't have this problem previously. I'm not sure what version number that was however.
 

Comment 1 by woxxom@gmail.com, Jun 26 2017

Might be a duplicate of  issue 736681  which is fixed in the source today so it'll be in the next canary update.
Cc: pnangunoori@chromium.org
Labels: Needs-Feedback
@jonpet2 - The fix has bee reverted, could you please check on the latest Canary available and let us know the behavior.

Thanks in advance.

Comment 3 by jonp...@gmail.com, Jun 27 2017

Version 61.0.3142.0 seems to work correctly, thank you.
Project Member

Comment 4 by sheriffbot@chromium.org, Jun 27 2017

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "pnangunoori@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 5 by ajha@chromium.org, Jun 28 2017

Status: WontFix (was: Unconfirmed)
Thanks for the update, closing as per C#2.

Sign in to add a comment