Canary All Pages Crash - Latest Build 2016-07-11
Reported by
clement....@gmail.com,
Jul 11 2016
|
|||
Issue description
Chrome Version :Unknown (Not Displaying). Latest Canary Release as of 2016-07-11.
URLs (if applicable) :
Other browsers tested:Mozilla Firefox, IE
have tested this issue:
Safari:
Firefox:OK
IE:OK
What steps will reproduce the problem?
(1)Opening Chrome
(2)
(3)
What is the expected result?
Functional Browser.
What happens instead?
No pages Displayed, including Webview menu pages.
Please provide any additional information below. Attach a screenshot if
possible.
System Configuration:
Acer FX-58M Intel X58 Bios-mods
Intel Core i7 920, 2.667Ghz Base 3.199.92Ghz Boost, 1.12V
6x2GB Samsung DDR3 1333Mhz 9-9-9-24-33 1.50V
ATI Radeon HD4850 1GB GDDR3 675Mhz Core 903Mhz Memory
Samsung 850 EVO 500GB SSD
Display: Packarg Bell Maestro 242Ws 1920x1080, 60Hz, 2ms GTG.
,
Jul 12 2016
I simply reinstalled again this morning with presumably a newer (newest) build, Version 54.0.2794.1 canary SyzyASan. The browser is now functional. chrome://settings was inaccessible as the page crashed when attempting to display as well. All extensions crashed on startup just like all of my tabs. chrome://crashes was inaccessible as well yesterday (same issue). With the new functional version installed, it unfortunately does not show any crash IDs since June 24, apparently none of yesterday's crashes were saved. The only documentation I seem to have about this would be the screenshot I posted along with the bug report, which is merely proof this was happening. I could have tested with another computer but purposely didn't update Chrome to be sure I had a functional browser on that computer. The current functional version on that computer is Version 54.0.2790.1 canary SyzyASan. Usually when I encounter big crashes like these (such as pages being displayed completely black), they happen on both of my computers given the same version. If there is more information I could gather (maybe crash reports saved as plain text somewhere), please let me know I'll be happy to follow through. Summary: The issue has been solved with release 54.0.2794.1
,
Jul 12 2016
Thank you for providing more feedback. Adding requester "brajkumar@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
,
Jul 15 2016
Thanks for your update, seems to be this issue might got fixed on latest canary build. Closing it for now ,please raise a new issue if you come across the similar one on latest chrome version. Thanks! |
|||
►
Sign in to add a comment |
|||
Comment 1 by brajkumar@chromium.org
, Jul 12 2016Labels: Stability-Crash Needs-Feedback