question-mark
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.

Chrome Dev-Tools error?

See original GitHub issue
Describe the issue / bug.

# the foloowing error was generated for chrome dev-tools

Debugger listening on ws://127.0.0.1:5858/1b82eabb-e1e6-4815-ba86-ac09e1c88c9e For help see https://nodejs.org/en/docs/inspector

[21394:0911/142528.962736:ERROR:CONSOLE(7323)] "Extension server error: Object not found: <top>", source: chrome-devtools://devtool s/bundled/inspector.js (7323)

[21394:0911/142529.961727:ERROR:CONSOLE(7323)] "Extension server error: Object not found: <top>", source: chrome-devtools://devtool s/bundled/inspector.js (7323)

[21394:0911/142530.391103:ERROR:CONSOLE(7323)] "Extension server error: Operation failed: http://localhost:9080/ has no execution c ontext", source: chrome-devtools://devtools/bundled/inspector.js (7323)

Tell me about your development environment.
  • Node version: 8.4.0
  • NPM version: 5.4.1
  • Operating System: Ubuntu 16.04 LTS

Issue Analytics

  • State:closed
  • Created 6 years ago
  • Comments:40 (1 by maintainers)

github_iconTop GitHub Comments

17reactions
stefnotchcommented, Mar 21, 2019

So, to summarize

In main/index.dev.js:

- require('electron-debug')({ showDevTools: true });
+ // NB: Don't open dev tools with this, it is causing the error
+ require('electron-debug')();

In main/index.js in the createWindow() function:

mainWindow.loadURL(winURL);

+  // Open dev tools initially when in development mode
+  if (process.env.NODE_ENV === "development") {
+    mainWindow.webContents.on("did-frame-finish-load", () => {
+      mainWindow.webContents.once("devtools-opened", () => {
+        mainWindow.focus();
+      });
+      mainWindow.webContents.openDevTools();
+    });
+  }
15reactions
adoji92commented, Oct 10, 2017

I had simliar issue

screenshot from 2017-10-10 18-01-35

with yarn (1.2.0) (yarn && yarn run dev)


surprisingly, with npm install && npm run dev, everything works fine (^^??) So if there is someone who suffers problem like me, try to use npm instead of yarn.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Error in Chrome DevTools - Stack Overflow
I have recently started to see a frequent error in Chrome Dev Tools when right clicking on an element for the purposes of...
Read more >
Issues: Find and fix problems - Chrome Developers
Use it to find solutions to problems detected by the browser, such as cookie issues and mixed content. If playback doesn't begin shortly,...
Read more >
Debugging with Chrome DevTools: Quick Front End Fixes
It requires both technical knowledge and data on the bug itself. Here are some quick tricks to solve Front End bugs with Chrome's...
Read more >
Using the Debug Console in Google Chrome to identify errors
Google Chrome's Debug console is a powerful tool that can help us identify the cause of the errors (displayed in red) and speed...
Read more >
Use Chrome DevTools to troubleshoot issues with your ads ...
Check for client-side errors · Visit the page that you want to investigate. · Open DevTools by right-clicking on the page and clicking...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found