Issue metadata
Sign in to add a comment
|
Chrome DevTools was disconnected from the page everytime during live console operation
Reported by
mr.varu...@gmail.com,
Oct 22
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.67 Safari/537.36 Steps to reproduce the problem: 1. Apply JS breakpoint on any AJAX response which returns a heavier JSON response 2. Try changing the value of returned data from console 3. The page gets crashed What is the expected behavior? I should be able to do live code edit without throwing disconnected from the page error What went wrong? I am trying to temper the JSON object using console, but unfortunately crome gets crashed. Happening every time since last Chrome update. Please suggest a solution, I am blocked. Thanks Did this work before? Yes Chrome version: 70.0.3538.67 Channel: stable OS Version: 10.0 Flash Version:
,
Oct 22
Sorry to hear that chrome is crashing. In order to help me reproduce the crash, could you be more specific about how big the JSON response is and what code you are running in the console to cause it to crash? You could also give us the id of your crash using these instructions: https://www.chromium.org/for-testers/bug-reporting-guidelines/reporting-crash-bug
,
Oct 23
mr.varunag@ Thanks for the issue. As per comment #2, request you to provide the details which will help in further triaging of the issue. Hence adding 'Needs-Feedback' label. Thanks..
,
Oct 23
I am able to reproduce the issue in very general javascript / jquery debugging. It is very frequently occurring today. Below is the given code snippet:
I added break-point on line no. 2 in below js function:
1. this.someFunctionName = function(element, isEl) {
2. var el = isEl ? element : angular.element(element),
3. isDependentField = el.closest(".tab-content").length;
4. .....more code
On Console, I tried to get the value of 'element' argument but 'Chrome DevTools was disconnected' error appeared. This is repeatedly coming for me for very simple cases.
For you reference I have generated the crash ID for the same issue: 7937eccc-7dea-4ec8-a825-9c1ab13017fe
,
Oct 23
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
,
Oct 23
Thanks for providing the details. Unfortunately, I did not find the report. Could you please send us the full ID line? e.g. "Uploaded Crash Report ID AAAAAAAAA (Local Crash ID: BBBBBBBB)" I think the "AAAAAAAA" part is what we need.
,
Oct 24
As per comment# 6, adding Needs-Feedback label to it. @Reporter: Could you please provide Crash ID as requested in comment# 6 and help in further investigating the issue. Please find the attached screenshot for reference. Thanks!
,
Oct 24
Please find attached screenshot of 3 crash ids captured yesterday. Hope this helps. Below are the ids shown in screenshot: Local Crash ID f31b5c90-a131-405a-aae0-5dab9040b05e Local Crash ID ebefc60f-0b42-4a32-b613-7a21c1b36047 Uploaded Crash Report ID 9b05ba081de652fd (Local Crash ID: 7937eccc-7dea-4ec8-a825-9c1ab13017fe) Hope this helps you troubleshoot the issue.
,
Oct 24
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
,
Oct 24
Thanks so much for the extra report IDs. The root cause of this crash was fixed in the past week. The V8 patch is part of M71, and should be picked up in M70 in the future. Merging with duplicate. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by phanindra.mandapaka@chromium.org
, Oct 22