ndb loads dev-tools window. But window stays empty and doesn't respond.

Tell us about your environment:

• ndb version: v1.0.42
• Platform / OS version: OSX 10.14.1
• Node.js version: 8.11.1
• using nodenv

Hey all 👋 After working with ndb successfully for a couple of months, it suddenly stopped working for me. running NDB loads the dev-tools screen, but then the window stays “empty”: sources pane shows no files. Console tab shows flashing caret, but typing anything and pressing enter does nothing. The node program that is supposed to run in the BG does not run.

I’ve also tried with a simple “hello world” js file, results are the same.

After a few minutes, the process will emit the following :

<--- Last few GCs --->

[14076:0x103000000]   318621 ms: Mark-sweep 1506.9 (1604.5) -> 1506.9 (1565.0) MB, 2302.6 / 0.4 ms  last resort GC in old space requested
[14076:0x103000000]   320195 ms: Mark-sweep 1506.9 (1565.0) -> 1506.9 (1565.0) MB, 1574.6 / 0.3 ms  last resort GC in old space requested


<--- JS stacktrace --->

==== JS stack trace =========================================

Security context: 0x3f62ebba57c1 <JSObject>
    1: /* anonymous */ [/Users/zappatta/.nodenv/versions/8.11.1/lib/node_modules/ndb/node_modules/chokidar/lib/fsevents-handler.js:~151] [pc=0x21b3e6e4ceb5](this=0x3f624758c571 <FSWatcher map = 0x3f62a00ae0a1>,watchPath=0x3f62c69c4d19 <String[100]: /Users/zappatta/Code/zencity-community/node_modules/es6-iterator/#/get.js/.npmignore/CHANGES/index.js>,realPath=0x3f62c6986929 <String[100]: /Users/zap...

FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory
 1: node::Abort() [/Users/zappatta/.nodenv/versions/8.11.1/bin/node]
 2: node::FatalException(v8::Isolate*, v8::Local<v8::Value>, v8::Local<v8::Message>) [/Users/zappatta/.nodenv/versions/8.11.1/bin/node]
 3: v8::internal::V8::FatalProcessOutOfMemory(char const*, bool) [/Users/zappatta/.nodenv/versions/8.11.1/bin/node]
 4: v8::internal::Factory::NewUninitializedFixedArray(int) [/Users/zappatta/.nodenv/versions/8.11.1/bin/node]
 5: v8::internal::(anonymous namespace)::ElementsAccessorBase<v8::internal::(anonymous namespace)::FastPackedObjectElementsAccessor, v8::internal::(anonymous namespace)::ElementsKindTraits<(v8::internal::ElementsKind)2> >::GrowCapacity(v8::internal::Handle<v8::internal::JSObject>, unsigned int) [/Users/zappatta/.nodenv/versions/8.11.1/bin/node]
 6: v8::internal::Runtime_GrowArrayElements(int, v8::internal::Object**, v8::internal::Isolate*) [/Users/zappatta/.nodenv/versions/8.11.1/bin/node]
 7: 0x21b3e6d042fd

another weird but potentially useful information: During those few minutes, I’m seeing a process named ndb/file_system hogging CPU on my machine.

using nodenv to switch to node 10.12.0, ndb seems to work fine.

If there is any more useful information I can provide, please let me know.

cheers 🍻

[ak239]

ndb@1.0.47 uses new version of chokidar. This version is much better optimized to work with huge file trees. Feel free to file another issue or leave a comment here if you still can reproduce this problem.

[rafakwolf]

Same here

node v8.15.0 Linux Mint v18.3 ndb v1.0.43

Thanks!