-
Notifications
You must be signed in to change notification settings - Fork 30.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
vscode-win32-ia32 build failure: JavaScript heap out of memory #29698
Comments
Hi @cleidigh. Try running |
@joaomoreno any other ideas? thanks |
Maybe let's start over:
What node version do you have installed? |
@joaomoreno while I can compile and execute code, I did just get an error log that doesn't seem to be fatal npm run gulp for Windows platform subsequently has the issue |
What makes you say this? It's not clear to me why npm is failing in your machine. First, running
These lines are very suspicious and can point as to why you're getting those errors. But in any case you seem to be able to compile and execute, so I don't think there's really a problem here. |
@joaomoreno here's the terminal output where I found the TSC Errors:
|
Oh I see. Have you tried |
Sorry for the bad dictation: I meant "package binary" This is the development sequence I use: git clean -xfd I have also tried -64 |
Have you tried |
Yes, tried that also, still get failures |
So, it's been our experience that I'm not really sure where all the TypeScript errors come from though. I ran out of ideas. 😕 |
Having the same issue with tsc Will post an update if I figure this out. |
@GharTok |
@joaomoreno |
@cleidigh What I reported earlier was on Windows 10. Today, on a working macos machine I ran git clean -xfd The errors start with TypeScript errors and end with npm ERR!... as follows:
Note: running node v7.4.0 and npm 4.0.5 |
@GharTok |
cc @mjbvz @jrieken Have you seen these errors?
|
This look like the errors you see when building with TypeScript. 2.4. Are you synced to a point after 96643e3 ? |
@cleidigh yes, scripts/npm install is the issue (both Windows 10 and macos) On macos I can now replicate the problem, so hopefully can isolate and fix it soon. EXISTING local VSCode project release/1.13 scripts/npm.sh install WORKS NEW VSCode Clone branch release/1.13 - Install FAILS
NEW VSCode Clone branch release/1.14 - Install WORKS
|
@GharTok Try cherry-picking 96643e3 into your local 1.13 branch and then running |
@mjbvz thanks - trying it now |
@mjbvz That worked - tried on two systems - Thank you very much! |
@mjbvz Per @joaomoreno suggestion packaging with: see error below: [13:37:50] [i18n] zh-cn has 142 untranslated strings.
errno: 'UNKNOWN', syscall: 'spawn' } } reason: { Error: spawn UNKNOWN
errno: 'UNKNOWN', syscall: 'spawn' } npm ERR! Windows_NT 6.1.7601 npm ERR! Please include the following file with any support request: |
@mjbvz |
OS: Windows 7 (VM 10GB memory)
Insiders source (June 27)
(Note: I have built the Win32 package before on the same machine, as recently as a month ago)
Building vscode OSS and executing from source succeeds.
Building vscode-win32-ia32 package fails near the end: see partial output below (full file attached)
The text was updated successfully, but these errors were encountered: