7

I'm working on React-native js and Xcode 9.3 for iOS app development, but in between I get this error:

Devtools error screenshot

while debugging and becomes a road blocker for me to proceed in the debugging. Also referred few articles from here but didn't get anything for help.

I read this link but it didn't work.

halfer
  • 19,824
  • 17
  • 99
  • 186
Lalit Dhiman
  • 71
  • 1
  • 1
  • 2
  • Please read [Under what circumstances may I add “urgent” or other similar phrases to my question, in order to obtain faster answers?](//meta.stackoverflow.com/q/326569) - the summary is that this is not an ideal way to address volunteers, and is probably counterproductive to obtaining answers. Please refrain from adding this to your questions. – halfer May 15 '18 at 09:13

3 Answers3

1

I'm having a similar issue today.

Try reloading and snapshotting the page in incognito mode. For me, some of my extensions were interfering with the snapshots, and loading the page w/out them helped.

Harrison Cramer
  • 3,792
  • 9
  • 33
  • 61
0

I had the same issue in my Angular App. I checked here Stack Overflow answer but it didn't help me. For me the thing was that I had a huge select multiple with a bunch of items. It was the reason that Chrome was throwing me that error since Chrome crash becouse of memory usage.. I read this article Crashing browsers with Angular2 DebugElement and it helped me with to found it out.

I hope this can help!

Lorena Pita
  • 1,366
  • 1
  • 17
  • 20
  • 1
    Hi @Lorena, Im facing same problem with angular application. Even im using huge select multiple with bunch of items. How did u solve it? – SVK Jan 25 '19 at 10:50
  • Hi @SVK, I reduced the amount of items lo load into the select multiple. – Lorena Pita Jan 28 '19 at 23:34
0

Install https://www.google.com/chrome/canary/ and run Visual Studio, on the debug-Run [Play] button open dropdown cl'ck on Browse and select new installed google chrome canary browser (C:\Users\username\AppData\Local\Google\Chrome SxS\Application\chrome.exe) as default debugger.

This worked for me.

H. Aydin
  • 340
  • 3
  • 10