Issue metadata
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 descriptionUserAgent: 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
,
Jan 13 2017
57.0.5979.0 downloaded automatically, canary now loads properly
,
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?
,
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
,
Jan 16 2017
,
Jan 17 2017
just to confirm 57.0.2983.0 has the same results for extensions and plug ins as 2981
,
Jan 17 2017
@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!
,
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
,
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
,
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
,
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
,
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
,
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
,
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.
,
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
,
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."
,
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.
,
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
,
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)
,
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
,
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
,
Feb 1 2017
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
,
Feb 2 2017
Please forgive my ignorance, I was unaware Dev channel was experimenting with a disabled plugins page, as well as DRM . .
,
Feb 10 2017
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
,
Mar 10 2017
Reporter@ - As per your comment #23 can we close this bug?
,
Mar 10 2017
Absolutely, this "bug" is no longer relevant, and should be closed
,
Mar 10 2017
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
,
Mar 21 2017
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 |
|||||||||||||||||||||
Comment 1 by lcape...@gmail.com
, Jan 12 20175.4 MB
5.4 MB Download
5.3 MB
5.3 MB Download