[TIMOB-27235] IOS: Having "DEBUG=*" flag causes the appc run node process to fail due to "Javascript heap out of memory"
GitHub Issue | n/a |
Type | Bug |
Priority | None |
Status | Open |
Resolution | Unresolved |
Affected Version/s | Release 8.1.0, Release 8.2.0 |
Fix Version/s | n/a |
Components | CLI, iOS |
Labels | n/a |
Reporter | Lokesh Choudhary |
Assignee | Eric Merriman |
Created | 2019-07-10T22:51:57.000+0000 |
Updated | 2019-07-15T09:51:43.000+0000 |
Description
Steps to reproduce:
1. Create a default classic app with the CLI using appc new
.
2. Make sure the tiapp.xml
has 8.2.0 SDK. I used 8.2.0.v2019071001261 & 8.1.0.v20190709083308.
3. From the terminal run DEBUG=* appc run -p ios -T simulator -l trace
. I have used simulator here but I guess it does not matter.
Actual results:
1. With DEBUG=*
flag we see a lot of babel
logging as transpiling is always on and eventually the build fails due to node running out of heap memory causing Javascript heap out of memory
.
2. This does not affect runs without DEBUG=*
flag which, directly does not affect out tooling. But, this flag is useful for looking at additional logging which is frequently used by us while testing & development.
3. Building to an Android device/emulator is fine.
Expected results:
1. Build does not fail with Javascript heap out of memory
when flag DEBUG=*
is used.
Attachments
If this might be down to the amount of logging from babel you can use
DEBUG=*,-babel
to remove the babel output