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

Issue 680404 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Last visit > 30 days ago
Closed: Mar 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug-Regression



Sign in to add a comment

canary 57.0.2978.0 won't load in win 7 home 64 bit

Reported by lcape...@gmail.com, Jan 12 2017

Issue description

UserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.87 Safari/537.36

Steps to reproduce the problem:
1. click canary icon
2. 
3. 

What is the expected behavior?
after I click the canary icon, the browser used to load, but not since 57.0.2975.0

What went wrong?
canary begins to load, same as  issue 679155 
canary starts to load for 5-7 seconds
canary abruptly closes

Crashed report ID: 1bae9a8f-5a31-416a-9b60-3eda9cc04d76.dmp 

How much crashed? Whole browser

Is it a problem with a plugin? N/A 

Did this work before? Yes before 57.0.2975.0

Chrome version: 57.0.2978.0  Channel: canary
OS Version: Windows 7, 
Flash Version: Shockwave Flash 24.0 r0
 

Comment 1 by lcape...@gmail.com, Jan 12 2017

here are 2 DMP files, hope they help

tried to open canary in incognito, same result
1bae9a8f-5a31-416a-9b60-3eda9cc04d76.dmp
5.4 MB Download
1ccd407d-6008-490a-94ab-c838437e74e2.dmp
5.3 MB Download

Comment 2 by lcape...@gmail.com, Jan 13 2017

57.0.5979.0 downloaded automatically, canary now loads properly

Comment 3 by lcape...@gmail.com, Jan 13 2017

All extensions are missing from extension list.

Adding extensions has been disabled in 57.02979.0  should I try to enable, if so, how?

Comment 4 by lcape...@gmail.com, Jan 14 2017

just to confirm, when I try to see extensions in 57.0.2981.0 I see:
Boo… You have no extensions :-( Want to browse the Chrome Web Store instead?

when I try to see plugins in 57.0.2981.0 I see:
"this site cannot be reached"  see attached screenshot
canary 57.0.2981.0 plug ins.JPG
20.4 KB View Download

Comment 5 by ajha@chromium.org, Jan 16 2017

Labels: Needs-Triage-M57

Comment 6 by lcape...@gmail.com, Jan 17 2017

just to confirm 57.0.2983.0 has the same results for extensions and plug ins as 2981

Comment 7 by hdodda@chromium.org, Jan 17 2017

Labels: Needs-Feedback
@lcapelis-- Could you please provide us the crash id and also try a system restart and chrome canary re-install and try with a fresh chrome profile without any extensions , and write us your observations .

Thanks!

Comment 8 by lcape...@gmail.com, Jan 17 2017

@hdodda-- There were no crash files on the dates I tested the 4 versions that kept closing on their own, but there were the 2 DMP files I have provided in the opening post, and comment 1. I did try reloading canary on all four versions 57.0.2975.0, through 2978.  The plugins and extensions anomolies showed up in 2979 through now 2984 as mentioned in comments 4 and 6.  

?? 

Thanks

Comment 9 by lcape...@gmail.com, Jan 19 2017

just to confirm: 57.0.2985.0  has the same results for extensions and plug ins as 2981 (see comment #4, 

thanks

Comment 10 by lcape...@gmail.com, Jan 20 2017

just to confirm: 57.0.2987.0  has the same results for extensions and plug ins as 2981 (see comment #4) 

thanks

Comment 11 by lcape...@gmail.com, Jan 21 2017

Just to confirm:  57.0.2987.4  has the same results for extensions and plug ins as 2981 (see comment #4) 

thanks

Comment 12 by lcape...@gmail.com, Jan 22 2017

Just to confirm:  57.0.2989.0 has the same results for extensions and plug ins as 2981 (see comment #4) 

thanks

Comment 13 by woxxom@gmail.com, Jan 22 2017

Your dump file from #4 loaded in VS2015 shows the callstack that crashes while performing sync in ConnectIfReady function inside shared_model_type_processor.cc

This function was reworked in r442978 (57.0.2979.0) to avoid crashes so the problem you're seeing after that seems to be caused by something else. So far it sounds like a corrupted profile or the entire "User Data" directory in %LocalAppData%\Google\Chrome

Comment 14 by lcape...@gmail.com, Jan 23 2017

FWW, the stable version of version 55.0.2883.87 m works correctly; I am unsure  what the remedy ought to be now (?) thanks for the response.

Comment 15 by lcape...@gmail.com, Jan 23 2017

 Just to confirm:  58.0.2990.0 has the same results for extensions and plug ins as 57.0.2981.0 (see comment #4) 

thanks

Comment 16 by woxxom@gmail.com, Jan 24 2017

I remember having a problem with Chrome not starting at all after the auto-update and I fixed it by running Chrome once with --reset-variation-state in the command line to "force a reset of the one-time-randomized FieldTrials on this client, also known as the Chrome Variations state."

Comment 17 by lcape...@gmail.com, Jan 24 2017

I uninstalled canary 58.0.2990.0 with Windows programs, installed 58.0.2990.1

Now extensions are present, like in stable chrome version, but chrome://plugins/chrome://plugins/
still returns the error message contained in the jpeg file attached to comment #4

I am unfamiliar with how to accomplish your instructions in comment #16, sorry . . I cannot find a tutorial on the syntax, how to start canary with a command line modification . . sorry.

Comment 18 by lcape...@gmail.com, Jan 25 2017

Just to confirm:  58.0.2991.0 has the same results for plug ins as 57.0.2981.0 (see comment #4, and attached jpeg) 

thanks
canary 57.0.2981.0 plug ins.JPG
20.4 KB View Download

Comment 19 by lcape...@gmail.com, Jan 25 2017

Just to confirm:  58.0.2992.0 has the same results for plug ins as 57.0.2981.0 (see comment #18)

Comment 20 by lcape...@gmail.com, Jan 27 2017

Just to confirm:  58.0.2994.0 (Official Build) canary (64-bit) has the same results for plug ins as 57.0.2981.0 (see comment #18, and attached jpeg) 

thanks

Comment 21 by lcape...@gmail.com, Jan 29 2017

Just to confirm:  58.0.2996.0 (Official Build) canary (64-bit) has the same results for plug ins as 57.0.2981.0 (see comment #18) 

thanks
58.0.2998.0
Just to confirm:  58.0.2998.0 (Official Build) canary (64-bit) has the same results for plug ins as 57.0.2981.0 (see comment #18) 

thanks
Please forgive my ignorance, I was unaware Dev channel was experimenting with a disabled plugins page, as well as DRM . . 
Project Member

Comment 24 by sheriffbot@chromium.org, Feb 10 2017

Labels: -Needs-Feedback Needs-Review
Owner: hdodda@chromium.org
Thank you for providing more feedback. Adding requester "hdodda@chromium.org" for another review and adding "Needs-Review" label for tracking.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Labels: -Needs-Review Needs-Feedback
Reporter@ - As per your comment #23 can we close this bug?

Comment 26 by lcape...@gmail.com, Mar 10 2017

Absolutely, this "bug" is no longer relevant, and should be closed
Project Member

Comment 27 by sheriffbot@chromium.org, Mar 10 2017

Cc: brajkumar@chromium.org
Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "brajkumar@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
Status: WontFix (was: Unconfirmed)
Thanks for the update.Closing this as of now, please report a new issue if you see any issue using chrome in future.

Sign in to add a comment