Skip to content
This repository has been archived by the owner on Aug 7, 2023. It is now read-only.

Uncaught Error: spawn ENOMEM #930

Closed
zdiehlio opened this issue Jun 2, 2017 · 1 comment
Closed

Uncaught Error: spawn ENOMEM #930

zdiehlio opened this issue Jun 2, 2017 · 1 comment

Comments

@zdiehlio
Copy link

zdiehlio commented Jun 2, 2017

[Enter steps to reproduce:]

  1. ...
  2. ...

Atom: 1.17.2 x64
Electron: 1.3.15
OS: Ubuntu 16.04.2
Thrown From: linter-eslint package 8.2.1

Stack Trace

Uncaught Error: spawn ENOMEM

At internal/child_process.js:313

Error: spawn ENOMEM
    at exports._errnoException (util.js:1026:11)
    at ChildProcess.spawn (internal/child_process.js:313:11)
    at exports.spawn (child_process.js:392:9)
    at Object.exports.fork (child_process.js:70:10)
    at new Task (/opt/atom/resources/app/src/task.js:43:1)
    at initializeESLintWorker (/packages/linter-eslint/main.js:136:21)

Commands

Non-Core Packages

busy-signal 1.4.1 
emmet 2.4.3 
intentions 1.1.2 
linter 2.0.0 
linter-eslint 8.2.1 
linter-ui-default 1.6.0 
@skylize
Copy link
Contributor

skylize commented May 8, 2018

Closing as duplicate of #927. Let us know if you have any further info that shows this to be a different isssue.

@skylize skylize closed this as completed May 8, 2018
@skylize skylize added the bug label May 8, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants