Can you close Canary and then launch it from the command line?

$ "/Applications/Google Chrome Canary.app/Contents/MacOS/Google Chrome Canary"

we'll then get any javascript errors on stderr. Can you copy them to this bug?

andre.michelle@ Thanks for the issue.

Tested this issue on Windows 10 and Mac OS 10.13.1 on the latest Canary 66.0.3345.0 and Stable 64.0.3282.140 and unable to reproduce the issue.

On launching Chrome and opening Devtools, can observe Devtools is rendering without any issues.
As per comment #2, request you to please relaunch chrome from command line and retry the issue and update the thread with the observations.

Thanks..

OUTPUT
[41630:39427:0213/074812.537843:ERROR:in_progress_cache_impl.cc(93)] Could not read download entries from file because there was a read failure.
2018-02-13 07:48:12.612 Google Chrome Canary[41630:28230067] *** Owner supplied to -[NSTrackingArea initWithRect:options:owner:userInfo:] referenced a deallocating object. Tracking area behavior is undefined. Break on NSTrackingAreaDeallocatingOwnerError to debug.
[41630:44803:0213/074813.062140:ERROR:upload_data_presenter.cc(73)] Not implemented reached in virtual void extensions::RawDataPresenter::FeedNext(const net::UploadElementReader &)
[41630:44803:0213/074813.090854:ERROR:upload_data_presenter.cc(73)] Not implemented reached in virtual void extensions::RawDataPresenter::FeedNext(const net::UploadElementReader &)
[41630:44803:0213/074813.267235:ERROR:upload_data_presenter.cc(73)] Not implemented reached in virtual void extensions::RawDataPresenter::FeedNext(const net::UploadElementReader &)
[41630:44803:0213/074813.551238:ERROR:upload_data_presenter.cc(73)] Not implemented reached in virtual void extensions::RawDataPresenter::FeedNext(const net::UploadElementReader &)

Thank you for providing more feedback. Adding requester "susan.boorgula@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

After starting Chrome Canary with the command-line, it worked for some time. But now it happened again. Starting in command-line now gives me:
[43894:37891:0213/120034.894816:ERROR:in_progress_cache_impl.cc(93)] Could not read download entries from file because there was a read failure.
2018-02-13 12:00:34.976 Google Chrome Canary[43894:28919804] *** Owner supplied to -[NSTrackingArea initWithRect:options:owner:userInfo:] referenced a deallocating object. Tracking area behavior is undefined. Break on NSTrackingAreaDeallocatingOwnerError to debug.
[43894:44803:0213/120035.425821:ERROR:upload_data_presenter.cc(73)] Not implemented reached in virtual void extensions::RawDataPresenter::FeedNext(const net::UploadElementReader &)
[43894:44803:0213/120035.449440:ERROR:upload_data_presenter.cc(73)] Not implemented reached in virtual void extensions::RawDataPresenter::FeedNext(const net::UploadElementReader &)
[43894:44803:0213/120035.676495:ERROR:upload_data_presenter.cc(73)] Not implemented reached in virtual void extensions::RawDataPresenter::FeedNext(const net::UploadElementReader &)
[43894:44803:0213/120035.956886:ERROR:upload_data_presenter.cc(73)] Not implemented reached in virtual void extensions::RawDataPresenter::FeedNext(const net::UploadElementReader &)
[43894:775:0213/120040.055308:ERROR:bad_message.cc(25)] Terminating renderer for bad IPC message, reason 169

And this time it does not fix it. The tools close immediately after opening.

andre.michelle@ Thanks for the issue.

Retried the issue on Windows 10 and Mac OS 10.12.6 on the latest Canary 66.0.3347.0 and unable to reproduce the issue.
Tried launching Chrome from command line as per comment #2 and can observe that Chrome is launched and can access Devtools without any issues. Cannot observe any errors as well.

As this issue is not reproducible at TE end, removing the Needs-Bisect label and requesting paulirish@ to please look into the issue and help in further triaging.

Thanks..

paulirish@ Request you to to please check the logs provided in comment #5 and #8 and provide an update on this issue.

Thanks..

A gentle ping..

paulirish@ Request you to please provide an update on this issue.

Thanks..

I am not sure if that ping is addressed in my direction. However it looks like I cannot reproduce this anymore. Might be fixed.

dgozman, do you see anything in the error output that is promising?

No idea, sorry. Perhaps, mac owners would know? Adding rsesek@.

The only thing that it could have been is "Terminating renderer for bad IPC message, reason 169".

Also do you have any window management utility apps or extensions installed?

As per comment#15 adding Needs-Feedback label.

@Reporter: Could you please respond to comment#15.

Thanks!

Can you please open chrome://crashes and post the server crash id for that crash (the one around 2018-02-13 12:00:34.976).

Also does it crash when you start it with a clean profile? e.g.

"/Applications/Google Chrome Canary.app/Contents/MacOS/Google Chrome Canary" --user-data-dir=/tmp/"`date`"

Closing as per comment #12 -- I don't think we can do anything here given it appears to be an isolated case and doesn't reproduce anymore.

Fair enough. I cannot reproduce it anymore either. If it happens again, I will file another bug.