Angular getting started devfile start / build commands are failing with exit code 137

Describe the bug

Angular getting started devfile start / build commands are failing with exit code 137

Che version

CRW 2.8 / samples from community devfiles 7.32.0

Steps to reproduce

1. go to http://workspaces.openshift.com/#get-started
2. start a new workspace based on the Node.js / Angular devfile
3. run yarn install command
4. run build command
5. ERROR: comand fails with error Command failed with exit code 137.

Expected behavior

build and start commands are not failing

Runtime

• workspaces.openshift.com

Screenshots

Eclipse Che Logs

yarn run v1.17.3
$ ng build --prod  --base-href ./ && cp CNAME dist/CNAME
Compiling @angular/platform-browser-dynamic : es2015 as esm2015
Compiling @angular/common/http : es2015 as esm2015
Compiling @angular/router : es2015 as esm2015
Compiling @angular/forms : es2015 as esm2015
Killed
Warning: Worker #1 exited unexpectedly (code: null | signal: SIGKILL).
  Current task: {entryPoint: @angular/platform-browser-dynamic, formatProperty: es2015, processDts: Yes}
  Current phase: compiling
error Command failed with exit code 137.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

[ericwill]

@ericwill well, it can but this means that the angular on http://workspaces.openshift.com/#get-started is going to be broken for 7+ days

Alright, instead of respinning I will backport the fix to the published devfile registry only

[ibuziuk]

thanks, folks verified on workspaces.openshift.com. Closing