Issue metadata
Sign in to add a comment
|
Random crash (Chrome has stopped working), no dump, Windows 10 1703
Reported by
timothy....@jhuapl.edu,
Jul 20
|
||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.99 Safari/537.36 Steps to reproduce the problem: Crashes occur randomly, with single tab. More frequent with multiple tabs. Cannot reproduce through a series of stepped events. What is the expected behavior? No crash state. What went wrong? Receive attached error, however no Report ID in Chrome. Reopen Chrome, and asks to restore pages so there is an awareness that Chrome process(es) died. All clients are running Windows 10 1703, fully patched and all running Chrome 67.0.3396.99 (Official Build) (64 bit) Crashed report ID: No How much crashed? Whole browser Is it a problem with a plugin? No Did this work before? Yes April/May Releases of Chrome Chrome version: 67.0.3396.99 Channel: stable OS Version: 10.0 Flash Version: - Cleared browser Cache - Disabled all browser Extensions - Turned off use of all Web Services (Nav Errors, Prediction, Protection) - Disabled, background apps on close. - Turned off hardware acceleration. - No Proxy settings - All other settings are default OOTB.
,
Jul 24
,
Jul 30
@jmukthavaram@chromium.org -there is no crash log or dump, to even provide an ID, its as if someone came along and task-killed the process. Additionally we've upgraded clients to the stable 68 release of Chrome and still experience the issue.
,
Jul 30
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jul 31
Tested on chrome # 67.0.3396.99, Stable #68.0.3440.75 on win 10.0 and not able to reproduce the issue. Steps followed: --------------- 1.Install chrome and open multiple urls. 2.Navigated all the urls successfully. @ timothy.alder: Thank you for the bug & update, But without a URl or testcase we can't debug the issue further. Please note if the URL is confidential please provide us a normal reduced test case(html) which exhibits the bug. Thanks you!
,
Aug 7
Which version of Windows 10 was tested? 1703? 1709? 1803? Microsoft released a patch for the July 2018 patch cycle which resolved the issue for 1803.
,
Aug 7
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Aug 31
I'm not sure why this has been marked Internals>GPU. robliao: can you triage this Windows crash?
,
Aug 31
Per #6 it sounds like it's no longer an issue. Without a crash id or a stack trace, there's not much we can do here. If there is more data, feel free to reopen and/or file a new issue with the required data and reference this bug. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by timothy....@jhuapl.edu
, Jul 20