Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

DevTools Error: Runtime.evaluate response did not contain a "result" object

See original GitHub issue

Initial URL: http://localhost:3000/excursion/199/SSRBT.R/2013-06-01 Chrome Version: 71.0.3578.98 Error Message: Runtime.evaluate response did not contain a “result” object Stack Trace:

Error: Runtime.evaluate response did not contain a "result" object
    at sendCommand.then.response (chrome-devtools://devtools/remote/serve_file/@15234034d19b85dcd9a03b164ae89d04145d8368/audits2_worker/audits2_worker_module.js:1044:47)

Issue Analytics

State:
Created 5 years ago
Comments:8 (2 by maintainers)

Top GitHub Comments

1reaction

brendankennycommented, Jan 4, 2019

as in https://github.com/GoogleChrome/lighthouse/issues/6026#issuecomment-423371703, still weird and shouldn’t happen, but the protocol may sometimes return things it shouldn’t 😃

The protocol can’t be completely dead because there was an id on the (connection-level) response matching it to the Runtime.evaluate call (and resolving the sendCommand promise), so something else is going on. Maybe we should stringify the response in the error message so at least we can see if it’s anything more than {}…but it might be just {} and it won’t be very helpful.

We should maybe dig into that chromium haystack to see if there are actually other possible responses 😃

0reactions

connorjclarkcommented, Dec 2, 2021

Seems this does not occur anymore.

Top Results From Across the Web

Runtime.evaluate response did not contain a "result" object

Channel: DevTools Initial URL: https://quotesdonut.com/ Chrome Version: 87.0.4280.141 Stack Trace: Error: Runtime.evaluate response did not ...

Possible side-effect in debug-evaluate in Google Chrome

A new bug in the latest version of Chrome triggers this event every time an expression is evaluated in DevTools. This includes live ......

chromedp - Go Packages

Package chromedp is a faster, simpler way to drive browsers supporting the Chrome DevTools Protocol in Go without external dependencies.

node_modules/puppeteer/lib/types.d.ts - devtools ... - Google Git

Blink - Chrome's rendering engine - has a concept of "accessibility tree", ... const result = await executionContext.evaluate(() => Promise.resolve(8 * 7))* ...

1295750 - console-entered error handling code is ... - Monorail

Specifically, the failure is that the underlying error objects are not passed to the handlers, as expected. What is the expected behavior? I ......