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

Inspected target disconnected #3832

Closed
paul-piro opened this issue Dec 16, 2015 · 15 comments
Closed

Inspected target disconnected #3832

paul-piro opened this issue Dec 16, 2015 · 15 comments

Comments

@paul-piro
Copy link

I keep getting this issue with latest version of electron 0.36.0. Latest electron build cannot be use with large projects which include requirejs and a lot of bower components. See screenshot, black window it's electron, this happens on both OSX and Windows
screenshot 2015-12-16 13 37 44

@zcbenz
Copy link
Member

zcbenz commented Dec 16, 2015

We have a few crashes in 0.36.0, they have been fixed on master branch and will be included in next release.

@zcbenz zcbenz closed this as completed Dec 16, 2015
@paul-piro
Copy link
Author

Ok thanks hope this one will be fixed too

@mattdesl
Copy link
Contributor

I am still getting inspector crashes on 0.36.4, should I file another bug?

@alistairheath
Copy link

I am having this issue with 0.36.4 and have narrowed it down to being caused by the serialport module. Unfortunately this a pretty vital part of the application so I can't remove it. Any suggestions? Thanks guys.

@jaycliff
Copy link

This issue is still persistent in win32 v0.36.7 (IA32), but is seemingly absent in the win32 x64 version.

@bhanuc
Copy link

bhanuc commented Feb 12, 2016

Issue persistent on windows 10-32 Bit using v0.36.7 electron-prebuilt

@filmerjarred
Copy link

Can confirm on windows10-64bit v0.36.7 electron-prebuilt.

Might be an unrelated issue, but narrowed it down to a weird place in my code, basically anytime a property of the global 'location' object is accessed using the 'load' module it crashes the program.

require('load').compiler("console.log(location.hostname)"); //Crashes electron
require('load').compiler("console.log(document.URL)"); //Works fine
require('load').compiler("console.log(location)"); //Works fine
eval("location.hostname"); //Works fine

@spalonytoster
Copy link

Issue persistent on Arch Linux using v0.36.8 electron-prebuilt

@Teddy-Schmitz
Copy link

Also encountered this on Arch Linux using v0.36.8 electron-prebuilt

@frenchbread
Copy link

Updated to electron-prebuilt@0.37.2. Still facing this issue in addition to black-screen..

@venomlust
Copy link

electron-prebuilt@0.37.2 same issue, after a few seconds instancing (my case Howler.js) and saving into another variable electron freeze and show black screen

@frenchbread
Copy link

Well, it seems that there is no black screen issue for me anymore. It took me to rewrite the whole application to figure out the issue.

First of all the app architecture is quite important if this is a multi-window app (like in my case).
But most importantly, after I've updated electron-prebuilt to version a 0.37.2 I forgot to change --version option in my build script. Referring to docs, this option is not required, but still.

So now, build scripts look like this:

"scripts": {
    "start": "electron app.js",
    "build-darwin": "electron-packager . appname --platform=darwin --arch=x64 --version=0.37.2 --ignore=node_modules/electron-*",
    "build-win32": "electron-packager . appname --platform=win32 --arch=x64 --version=0.37.2 --ignore=node_modules/electron-*"
}

App builds work well on both MacOSX & Windows 10.

@spalonytoster
Copy link

electron-prebuilt@0.37.2 now works like a charm. I'm on Arch Linux x64.

@KT071
Copy link

KT071 commented May 24, 2016

Still have that problem on electron 1.0.0 ;/

@jaycliff
Copy link

It seems like this issue is electron-specific (or perhaps chromium-specific), since the latest version of Chrome (51.0.2704.84) doesn't exhibit this behaviour. I am using howler.js (v2 beta) to load up some audio files in my project which somehow triggers the issue, but doesn't happen at all in Chrome.

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

No branches or pull requests