DevTools was disconnected from the page - React development , Console JS

[julien keruzec]

Dear All,

I have some issue with Chrome. I'm currently developping an app with React JS.

When I have a breakpoint in my code and when I want to debug something in console. I just start typing and get Chrome crash with message :

"DevTools was disconnected from the page.

Once page is reloaded, DevTools will automatically reconnect."

This bug is not here everytime I start typing on console.

can someone help with that?

Thanks,

Julien.

[PhistucK]

Can you retry with a new profile?

☆PhistucK

--
--
Chromium Discussion mailing list: chromium...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-discuss

---
You received this message because you are subscribed to the Google Groups "Chromium-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-discu...@chromium.org.

[julien keruzec]

I did some test with new profile using "--user-data-dir" option and another directory.

I had the same bug .... with fresh Chrome settings.

I'm using "--disable-web-security" also.

And I plugged my JS workspace with my file system.

[PhistucK]

> This bug is not here everytime I start typing on console.

Do you mean it is inconsistent?

Does it happen in other websites as well?

☆PhistucK

--

[julien keruzec]

Yes it's kind of inconsistent. I can't find a valid pattern/scenario to reproduce it everytime.

I'm using mostly the console/Dev Tools for my own app that I daily develop so I can't tell if I can reproduce it on other website/webapp.

I use Chrome since 5 years or so, and never had this kind of problem before.

Le mardi 23 octobre 2018 11:27:44 UTC+2, julien keruzec a écrit :

[PhistucK]

Maybe something in your page is triggered by the automatic completion (it eagerly evaluates and inspects JavaScript objects for that) that causes the crash.

You can try and disable eager evaluation (in the settings of the console), but that may avoid the problem at the cost of a useful feature, so -

You can search crbug.com for an existing issue and star it. If you cannot find one, file a new issue using the "New issue" link on the same page.

Please, do not add a "+1" or "Me too" or "Confirmed" (or similar) comment. It just wastes the time of Chrome engineers and sends unnecessary e-mails to all of the people who starred the issue.

You can reply with a link to the found or created issue and might get triaged (and fixed) faster.

Thank you.

☆PhistucK

--

[julien keruzec]

Ok I didn't find any existing issue, so I created one : 

https://crbug.com/898759

Thanks for your help :)

Le mardi 23 octobre 2018 11:27:44 UTC+2, julien keruzec a écrit :

[philip...@snapengage.com]

This started happening to me about 1-2 months ago.  When I upgraded from Chrome 68 to 69.  It happens when I have the SOURCES tab open and I am stepping through my local React/Redux code.  I upgrade from 69 to 70 with no success.  I tried Canary.  I tried removing & uninstalling Chrome.  Upgrading OS to Mojave too.  

The error: 

"DevTools was disconnected from the page.

Once page is reloaded, DevTools will automatically reconnect."

Is completely random it seems.

I have sent multiple "Report an Issue" reports through chrome but no response.  Any ideas?  Using Firefox as an alternate is just not as good but it's better than crashing.

THANKS!