search

adobe / brackets

An open source code editor for the web, written in JavaScript, HTML and CSS.
http://brackets.io
MIT License
33.26k stars 7.63k forks source link

Failed to connect to Node #7806

Open ingorichter opened 10 years ago

ingorichter commented 10 years ago

Re-run failing tests will result in this error. This happens sometimes for the 1st re-run, sometimes it will appear with on a later run.

The test window and brackets can't be properly closed anymore. I have to force quit Brackets.

This happened on OSX 10.9.2.

The errormessage in the console is

[NodeDomain] Error loading domain "fileWatcher": Unable to load one of the modules: /Users/irichter/develop/fun/OSS/brackets/test/../src/filesystem/impls/appshell/node/FileWatcherDomain, reason: Maximum call stack size exceeded NodeDomain.js:146

screenshot 2014-05-09 13 18 37

pthiess commented 10 years ago

High priority - nominating for release 40 since this when we try to get 1750 in. Assigning to @bchintx.

njx commented 10 years ago

@pthiess It looks like this is assigned to @ingorichter now - was that intentional?

pthiess commented 10 years ago

@njx I haven't reassigned it to @ingorichter - Ingo?

ingorichter commented 10 years ago

This was assigned to me during daily standup.

ingorichter commented 10 years ago

Short update: I had the same issue today with CEF 1916, but it went away after I used Brackets without any extension installed. Need to further investigate which extension is causing the issues.

bchintx commented 10 years ago

FYI- I grabbed the 1750 branch on Windows, but I'm not seeing the node connection error. I'll check Mac next.

njx commented 10 years ago

BTW, I just noticed (on Mac) that when I got this error, there was another error before it in the console:

[NodeDomain] Error loading domain "fileWatcher": Unable to load one of the modules: /Users/nj/github/brackets-shell/xcodebuild/Release/Brackets.app/Contents/dev/test/../src/filesystem/impls/appshell/node/FileWatcherDomain, reason: Maximum call stack size exceeded

JeffryBooher commented 9 years ago

Removing this as a CEF issue since I had never seen this with CEF 1750 and it appears that it may have been related to an extension according to Ingo's notes. @ingorichter can you look at this with the 2171 branch and update accordingly?