Constant "Aw, Snap' and 'Out of Memory" errors while using Dev Tools.
Reported by
mwei...@561media.com,
Jun 22 2018
|
|||||
Issue description
Chrome Version : 67.0.3396.87
OS Version: 10.0
URLs (if applicable) :
Other browsers tested:
Add OK or FAIL after other browsers where you have tested this issue:
Safari:
Firefox: OK
IE/Edge:OK
What steps will reproduce the problem?
1. Open tabs
2. Open Dev tools
3. Inspect elements
What is the expected result? Normal operation
What happens instead of that? Aw Snap error, Out of Memory error
Please provide any additional information below. Attach a screenshot if
possible.
Local web development using VS Code and licensed version of MAMP Pro. Regular mode or incognito, doesn't matter. Multiple tabs open, inspect elements, crashes on multiple pagaes.
UserAgentString: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.87 Safari/537.36
,
Jun 25 2018
Unable to reproduce the issue on Win-10 using chrome reported version #67.0.3396.87. Following are the steps followed to reproduce the issue. ------------ 1. Opened tabs 2. Opened Dev tools 3. Inspected elements 4. Observed that there was no aw snap error or out of memory error. reporter@ - Could you please provide crash id from chrome://crashes for further triaging from TE-end. Thanks...!!
,
Jun 25 2018
There were a multitude of crash ids but here are a handful: Local Crash ID: cc117422-86f4-405c-9635-5a190edcfe70 (Uploaded Crash Report ID ea86a9dc1f08a8a7) Local Crash ID: 4a4a1ad8-cae0-4747-86ab-a6d9b0f96115 (Uploaded Crash Report ID c796ef3c8beaaeed) Local Crash ID: d686f03e-e606-489c-aa82-99bf2fd4a7ab (Uploaded Crash Report ID 04ccdc4e272ee511) Local Crash ID 2b7eca5f-0c8d-49a6-9141-ba040e9da6e1 Local Crash ID baf15230-aa3c-4984-96df-d7f3d87daba2
,
Jun 25 2018
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
,
Jun 26 2018
As per comment# 3 from the reporter, as crash id's has been provided, hence routing this issue to Inhouse for further investigation on this issue and adding TE-NeedsTriageFromHYD label to it. Thanks!
,
Jun 27 2018
mweiser@, Thanks for the reply. As per the above provided crash id(ea86a9dc1f08a8a7),issue seems to be similar to #850781 hence merging into it. Please feel free to undup if it is not similar.
,
Jun 27 2018
Please provide permission to view issue #850781 so I can review follow.
,
Jun 28 2018
"Aw, Snap' and 'Out of Memory" errors are still constantly shutting down Chrome. Is there any way to follow the progress of issue #850781? |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by krajshree@chromium.org
, Jun 24 2018