New issue
Advanced search Search tips

Issue 837937 link

Starred by 2 users
Status: Duplicate
Merged: issue 838503
Owner: ----
Closed: May 2018
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 3
Type: Bug



Sign in to add a comment

Uncaught TypeError: Cannot convert undefined or null to object

Reported by apple.cs...@gmail.com, Apr 28 2018 
Chrome Version       : 66.0.3359.139
OS Version: 10.0
URLs (if applicable) :
Other browsers tested:
  Add OK or FAIL after other browsers where you have tested this issue:
     Safari:OK
    Firefox:OK
    IE/Edge:OK

What steps will reproduce the problem?
1.
2.
3.

What is the expected result?
It should not be show the "" when debugging the javascript file because the condition is correct inside the javascript code. There is no problem when debugging with other browser.

What happens instead of that?
When start debugging the "Uncaught TypeError" shows. The devtool says to relod the page and it crashes. 

Please provide any additional information below. Attach a screenshot if
possible.
The code works well and no error show when browsing the local html file which I have been developing. But the error appears only when debugging the javascript code. It shows "Uncaught TypeError: Cannot convert undefined or null to object".
When the debugging process pause near to the break point, If I click F8 button then it also not show the error But If Press F10 button for Step forward the debugging Then it shows the error.
Again I am saying that, other browser have no such problem and only chrome shows such error only when debugging.

UserAgentString: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.139 Safari/537.36
After click checkbox.png
118 KB View Download
After click resume debugging .png
114 KB View Download
After click resume debugging no error .png
116 KB View Download
After click step forward .png
123 KB View Download
crash page.png
108 KB View Download

Comment 1 by krajshree@chromium.org, Apr 30 2018

Labels: Needs-Triage-M66

Comment 2 by dtapu...@chromium.org, Apr 30 2018

Components: Platform>DevTools

Comment 3 by neophyto...@gmail.com, Apr 30 2018 

I have the same problem. It started 2 days ago, all of a sudden, in all 3 of our deveoper PCs. The problem manifests itself in different parts of the code (parts of the code which have been working for months).
The Chrome release is the same as the one reported (66.0.3359.139).
The problem is impacting our productivity immensely as the Chrome developer tools are our main debugging tools.

Comment 4 by krajshree@chromium.org, May 7 2018

Labels: Triaged-ET
Mergedinto: 838503
Status: Duplicate (was: Unconfirmed)
The issue seems to be similar to issue id: 838503. Hence, merging into issue id: 838503.

Thanks...!!
►

Sign in to add a comment