Issue metadata
Sign in to add a comment
|
Browser crashes upon trying to open
Reported by
nick.cip...@gmail.com,
Apr 12 2017
|
||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.116 Safari/537.36 Edge/15.16170 Steps to reproduce the problem: 1. Update to 59.0.3068.1 2. The browser should crash when it is automatically re-opening or when you try to open it yourself 3. What is the expected behavior? The browser opens What went wrong? The browser pops up then disappears. Crashed report ID: Client ID: -8672337501480884681 How much crashed? Whole browser Is it a problem with a plugin? N/A Did this work before? Yes Chrome version: 59.0.3068.1 Channel: canary OS Version: 10.0 Flash Version: This was in my 'debug.log' file: [0411/201534.002:ERROR:process_info.cc(626)] range at 0x2fc429f000000000, size 0x197 fully unreadable [0411/201534.002:ERROR:process_info.cc(626)] range at 0x2fc42a1000000000, size 0x197 fully unreadable [0411/201534.002:ERROR:process_info.cc(626)] range at 0x0, size 0x197 fully unreadable [0411/201539.295:ERROR:process_info.cc(626)] range at 0x6bd6294000000000, size 0x2e8 fully unreadable [0411/201539.311:ERROR:process_info.cc(626)] range at 0x6bd6296000000000, size 0x2e8 fully unreadable [0411/201539.311:ERROR:process_info.cc(626)] range at 0x0, size 0x2e8 fully unreadable [0411/201543.182:ERROR:process_info.cc(626)] range at 0x1ec294000000000, size 0x147 fully unreadable [0411/201543.182:ERROR:process_info.cc(626)] range at 0x1ec296000000000, size 0x147 fully unreadable [0411/201543.182:ERROR:process_info.cc(626)] range at 0x0, size 0x147 fully unreadable [0411/201550.034:ERROR:process_info.cc(626)] range at 0xc044294000000000, size 0x1d4 fully unreadable [0411/201550.034:ERROR:process_info.cc(626)] range at 0xc044296000000000, size 0x1d4 fully unreadable [0411/201550.034:ERROR:process_info.cc(626)] range at 0x0, size 0x1d4 fully unreadable [0411/202636.116:ERROR:process_info.cc(626)] range at 0x160f294000000000, size 0x191 fully unreadable [0411/202636.116:ERROR:process_info.cc(626)] range at 0x160f296000000000, size 0x191 fully unreadable [0411/202636.116:ERROR:process_info.cc(626)] range at 0x0, size 0x191 fully unreadable [0411/202717.969:ERROR:process_info.cc(626)] range at 0x5d8a28e200000000, size 0x2a2 fully unreadable [0411/202717.969:ERROR:process_info.cc(626)] range at 0x5d8a290200000000, size 0x2a2 fully unreadable [0411/202717.969:ERROR:process_info.cc(626)] range at 0x0, size 0x2a2 fully unreadable [0411/203420.782:ERROR:process_info.cc(626)] range at 0x2845294000000000, size 0x256 fully unreadable [0411/203420.782:ERROR:process_info.cc(626)] range at 0x2845296000000000, size 0x256 fully unreadable [0411/203420.782:ERROR:process_info.cc(626)] range at 0x0, size 0x256 fully unreadable [0411/203425.377:ERROR:process_info.cc(626)] range at 0xed13294000000000, size 0x1c4 fully unreadable [0411/203425.378:ERROR:process_info.cc(626)] range at 0xed13296000000000, size 0x1c4 fully unreadable [0411/203425.378:ERROR:process_info.cc(626)] range at 0x0, size 0x1c4 fully unreadable [0411/203507.419:ERROR:process_info.cc(626)] range at 0x995d294000000000, size 0x202 fully unreadable [0411/203507.419:ERROR:process_info.cc(626)] range at 0x995d296000000000, size 0x202 fully unreadable [0411/203507.419:ERROR:process_info.cc(626)] range at 0x0, size 0x202 fully unreadable [0411/203846.871:ERROR:process_info.cc(626)] range at 0xd884294000000000, size 0x1ef fully unreadable [0411/203846.872:ERROR:process_info.cc(626)] range at 0xd884296000000000, size 0x1ef fully unreadable [0411/203846.872:ERROR:process_info.cc(626)] range at 0x0, size 0x1ef fully unreadable [0411/203858.075:ERROR:process_info.cc(626)] range at 0x5219289800000000, size 0x124 fully unreadable [0411/203858.076:ERROR:process_info.cc(626)] range at 0x5219289a00000000, size 0x124 fully unreadable [0411/203858.076:ERROR:process_info.cc(626)] range at 0x0, size 0x124 fully unreadable
,
Apr 12 2017
,
Apr 12 2017
I am not seeing anything in crash server with the above client id. nick.cipriani@: If this crash is listed under chrome://crashes, could you please attach also server id from there.
,
Apr 12 2017
I looked under chrome://crashes and nothing shows up there even after I enabled crash reporting in the new, working chrome window. I did find 21 .dmp files in the User Data\Crashpad folder, all from today and yesterday. I have attached the most recent one, I hope it helps! If not, let me know what other data I can provide or where the proper crash reports would be saved.
,
Apr 12 2017
Thank you for providing more feedback. Adding requester "ajha@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
,
Apr 13 2017
Happy to report that version 59.0.3069.0 fixes the issue and no longer crashes!
,
Apr 13 2017
As per comment#6 changing the status as Wontfix. nick.cipriani@ please feel free to file a new bug if you face the issue again. Thanks.. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by nick.cip...@gmail.com
, Apr 12 2017