Confusing ENOMEM error when spawning the GNU/Linux drive detection script
See original GitHub issue- Etcher version: 1.0.0-beta.18
- Operating system and architecture: Ubuntu 14.04
Running Etcher to get Ubuntu 16.04 on a 4GB USB key I get the following error:
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.execFile (child_process.js:155:15)
at Object.module.(anonymous function) [as execFile] (ELECTRON_ASAR.js:224:18)
at Object.exports.run (/tmp/.mount_ZZ2t46/usr/bin/resources/app.asar/node_modules/drivelist/lib/scripts.js:84:16)
at Object.exports.list (/tmp/.mount_ZZ2t46/usr/bin/resources/app.asar/node_modules/drivelist/lib/drivelist.js:56:11)
at Object.tryCatcher (/tmp/.mount_ZZ2t46/usr/bin/resources/app.asar/node_modules/bluebird/js/release/util.js:16:23)
at Object.ret [as listAsync] (eval at makeNodePromisifiedEval (/tmp/.mount_ZZ2t46/usr/bin/resources/app.asar/node_modules/bluebird/js/release/promisify.js:184:12), <anonymous>:13:39)
at isElevated.then.then (/tmp/.mount_ZZ2t46/usr/bin/resources/app.asar/lib/cli/etcher.js:70:20)
at tryCatcher (/tmp/.mount_ZZ2t46/usr/bin/resources/app.asar/node_modules/bluebird/js/release/util.js:16:23)
at Promise._settlePromiseFromHandler (/tmp/.mount_ZZ2t46/usr/bin/resources/app.asar/node_modules/bluebird/js/release/promise.js:504:31)
at Promise._settlePromise (/tmp/.mount_ZZ2t46/usr/bin/resources/app.asar/node_modules/bluebird/js/release/promise.js:561:18)
at Promise._settlePromise0 (/tmp/.mount_ZZ2t46/usr/bin/resources/app.asar/node_modules/bluebird/js/release/promise.js:606:10)
at Promise._settlePromises (/tmp/.mount_ZZ2t46/usr/bin/resources/app.asar/node_modules/bluebird/js/release/promise.js:685:18)
at Async._drainQueue (/tmp/.mount_ZZ2t46/usr/bin/resources/app.asar/node_modules/bluebird/js/release/async.js:138:16)
at Async._drainQueues (/tmp/.mount_ZZ2t46/usr/bin/resources/app.asar/node_modules/bluebird/js/release/async.js:148:10)
at Immediate.Async.drainQueues (/tmp/.mount_ZZ2t46/usr/bin/resources/app.asar/node_modules/bluebird/js/release/async.js:17:14)
at runCallback (timers.js:574:20)
at tryOnImmediate (timers.js:554:5)
at processImmediate [as _immediateCallback] (timers.js:533:5)
Issue Analytics
- State:
- Created 7 years ago
- Comments:14 (12 by maintainers)
Top Results From Across the Web
Confusing ENOMEM error when spawning the GNU/Linux drive ...
Thanks for reporting. The error indicates you didn't have enough memory for a certain child process (the drive detection script in this case)...
Read more >Node.js catch ENOMEM error thrown after spawn
js script crashes because of a thrown ENOMEM (Out of memory) errnoException when using spawn. The error: child_process.js:935 throw errnoException(process.
Read more >[PATCH] /fs/partition/check.c: fix return value warning - Google Groups
XFS filesystems are mounted. So I decided to try and implement the infrastructure to do this. Please let me know what you think,...
Read more >Diff - d7824370e26325c881b665350ce64fb0a4fde24a^^2 ...
-130,8 +130,6 @@ - information on EDAC - Error Detection And Correction ... in the +subdirectories of 'scripts/coccinelle' to the entire Linux kernel....
Read more >Bug listing with status RESOLVED with resolution OBSOLETE ...
Bug :1523 - "[IDEA] Offload work by distributing trivial ebuild ... Bug:262154 - "sys-block/iscsitarget-0.4.17 init script does not detect start up failures" ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Yeah, that’d be really helpful!
Definitely. We have some human friendly translations here: https://github.com/resin-io/etcher/blob/master/lib/cli/errors.js#L27, but we’re not addressing the ENOMEM one.
Right. The stack trace says
/tmp/.mount_ZZ2t46/usr/bin/resources/app.asar/lib/cli/etcher.js
, which means it’s coming from the latest drive check from the writer process before starting the flash. Thanks a lot @keunes , this should be more than enough for us to clarify the error.