VSCodium / vscodium

binary releases of VS Code without MS branding/telemetry/licensing
https://vscodium.com
MIT License
25.06k stars 1.07k forks source link

Error: EMFILE: too many open files, open '/tmp/yaourt-tmp-fabio/aur-vscodium/src/vscode/out-build/vs/base/browser/ui/selectBox/selectBoxCustom.js.map' #1808

Open FabioNevesRezende opened 7 months ago

FabioNevesRezende commented 7 months ago

Describe the bug Can't build Vscodium from AUR (arch user repository)

Please confirm that this problem is VSCodium-specific

Please confirm that the issue/resolution isn't already documented

To Reproduce Steps to reproduce the behavior:

Expected behavior Successful build of the application

Desktop (please complete the following information):

Additional context Error stack:


[14:02:42] Starting optimize-vscode ...
[14:02:48] 'minify-vscode' errored after 5.87 s
[14:02:48] Error: EMFILE: too many open files, open '/tmp/yaourt-tmp-fabio/aur-vscodium/src/vscode/out-build/vs/base/browser/ui/selectBox/selectBoxCustom.js.map'
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
+++ error_function build
+++ ((  ! BASH_SUBSHELL  ))
++++ gettext 'A failure occurred in %s().'
+++ error 'A failure occurred in %s().' build
+++ local 'mesg=A failure occurred in %s().'
+++ shift
++++ gettext ERROR:
+++ printf '==> ERROR: A failure occurred in %s().\n' build
==> ERROR: A failure occurred in build().
++++ gettext Aborting...
+++ plainerr Aborting...
+++ plain Aborting...
+++ ((  QUIET  ))
+++ local mesg=Aborting...
+++ shift
+++ printf '    Aborting...\n'
    Aborting...
+++ exit 4
+ clean_up
+ local EXIT_CODE=4
+ ((  INFAKEROOT  ))
+ [[ -p '' ]]
+ ((  (EXIT_CODE == E_OK || EXIT_CODE == E_INSTALL_FAILED) && BUILDPKG && CLEANUP  ))
+ remove_deps
+ ((  ! RMDEPS  ))
+ return 0
+ exit 4
==> ERROR: Makepkg was unable to build vscodium.
Andyloris commented 7 months ago

I have the same problem, on the same platform. Has anybody found a solution ?

github-actions[bot] commented 4 weeks ago

This issue has been automatically marked as stale. If this issue is still affecting you, please leave any comment, and we'll keep it open. If you have any new additional information, please include it with your comment!