ndb crashes after launching script

Steps to reproduce: I’m launching ndb with ndb bot.js and it launches, starts the script and crashes, the same when i click “start” inside ndb and for example toggle “pause on exceptions” or change tab.

• ndb version: 1.0.37
• Platform / OS version: Microsoft Windows [Version 10.0.17134.407]
• Node.js version: 10.14.1

There seems to be no problem with code since it works on normal node, but when i open it in ndb, then it crashes.

What happens instead?

ndb throws: events.js:167 throw er; // Unhandled ‘error’ event ^

Error [ERR_IPC_CHANNEL_CLOSED]: Channel closed at ChildProcess.target.send (internal/child_process.js:628:16) at Rpc.routeMessage_ (C:\Users\user\AppData\Roaming\npm\node_modules\ndb\node_modules\carlo\rpc\rpc.js:379:9) at page_.exposeFunction.data (C:\Users\user\AppData\Roaming\npm\node_modules\ndb\node_modules\carlo\lib\carlo.js:327:71) at Page._onBindingCalled (C:\Users\user\AppData\Roaming\npm\node_modules\ndb\node_modules\puppeteer-core\lib\Page.js:516:56) at CDPSession.Page.client.on.event (C:\Users\user\AppData\Roaming\npm\node_modules\ndb\node_modules\puppeteer-core\lib\Page.js:134:54) at CDPSession.emit (events.js:182:13) at CDPSession._onMessage (C:\Users\user\AppData\Roaming\npm\node_modules\ndb\node_modules\puppeteer-core\lib\Connection.js:216:12) at Connection._onMessage (C:\Users\user\AppData\Roaming\npm\node_modules\ndb\node_modules\puppeteer-core\lib\Connection.js:99:19) at PipeTransport._dispatch (C:\Users\user\AppData\Roaming\npm\node_modules\ndb\node_modules\puppeteer-core\lib\PipeTransport.js:65:24) at Socket.PipeTransport._eventListeners.helper.addEventListener.buffer (C:\Users\user\AppData\Roaming\npm\node_modules\ndb\node_modules\puppeteer-core\lib\PipeTransport.js:30:64) Emitted ‘error’ event at: at process.nextTick (internal/child_process.js:632:35) at process._tickCallback (internal/process/next_tick.js:61:11)

I’ve tried re-installing ndb, reinstalling all dependencies, reinstalling ms build tools, different flags and stuff. It did work, but lately stopped.

I can add that when this started occuring, the ndb got slow, instead of showing my files immediately, it showed them after 10s, and there are windows popping up, which weren’t before (node.EXE and npm)

Thanks in advance.

[darcyparker]

I had same problem on Debian, and found I had to run:

 sudo sysctl -w kernel.unprivileged_userns_clone=1

https://github.com/GoogleChrome/puppeteer/blob/ff6d2a33f3edb8837bde3ab687c6d06510b5d4de/docs/troubleshooting.md#setting-up-chrome-linux-sandbox

In my case it is for a dev machine, so I am not too worried about changing this option.

[vaxerski]

reverted to ndb@1.0.13 - everything’s fine.

EDIT: ndb@1.0.17 - still fine