Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DevTools Error: Cannot read property 'value' of undefined #6026

Closed
StructByLightning opened this issue Sep 15, 2018 · 5 comments
Closed

DevTools Error: Cannot read property 'value' of undefined #6026

StructByLightning opened this issue Sep 15, 2018 · 5 comments

Comments

@StructByLightning
Copy link

Initial URL: https://www.parahumans.net/
Chrome Version: 69.0.3497.92
Error Message: Cannot read property 'value' of undefined
Stack Trace:

TypeError: Cannot read property 'value' of undefined
    at sendCommand.then.result (chrome-devtools://devtools/remote/serve_file/@eb2c6d16bcb960cc5c322243c1771713460c4bcf/audits2_worker/audits2_worker_module.js:1008:211)
@brendankenny
Copy link
Member

Something went pretty wrong here. This is the result on the response from sendCommand('Runtime.evaluate', ...), which should always exist, even if it was returning an error.

I don't see any other instances in the error logs for this. Are you still seeing this problem or was it transient?

@StructByLightning
Copy link
Author

That's interesting. Trying to audit the page still gave me an error. If I clicked retry, again, same error. But if instead if I clicked cancel and went to the console, then went back and tried another audit, it worked. I checked to see if I could duplicate this behavior on a fresh tab but it worked perfectly the first time. There's definitely something wrong somewhere but if it can't be duplicated I guess there's nothing to be done.

@wardpeet
Copy link
Collaborator

wardpeet commented Oct 8, 2018

@exterkamp is this one fixed? Seems you created a pr for it.

@exterkamp
Copy link
Member

It is but it is not landed in production Chrome yet so audit panel users will still see this error for the time being.

@exterkamp
Copy link
Member

Closing, because this should be in stable Chrome M71+ (v3.2.0+). We can reopen if this still comes up!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants