When I try to run bench build --force give me this error!

bench build --force

Linking /cloudclusters/erpnext/frappe-bench/apps/frappe/frappe/public to ./assets/frappe
Linking /cloudclusters/erpnext/frappe-bench/apps/frappe/node_modules to ./assets/frappe/node_modules
Linking /cloudclusters/erpnext/frappe-bench/apps/erpnext/erpnext/public to ./assets/erpnext
Linking /cloudclusters/erpnext/frappe-bench/apps/erpnext/node_modules to ./assets/erpnext/node_modules
Linking /cloudclusters/erpnext/frappe-bench/apps/lms/lms/public to ./assets/lms
Linking /cloudclusters/erpnext/frappe-bench/apps/lms/node_modules to ./assets/lms/node_modules
Linking /cloudclusters/erpnext/frappe-bench/apps/chat/chat/public to ./assets/chat
Linking /cloudclusters/erpnext/frappe-bench/apps/hrms/hrms/public to ./assets/hrms
Linking /cloudclusters/erpnext/frappe-bench/apps/hrms/node_modules to ./assets/hrms/node_modules
Linking /cloudclusters/erpnext/frappe-bench/apps/webshop/webshop/public to ./assets/webshop
Linking /cloudclusters/erpnext/frappe-bench/apps/payments/payments/public to ./assets/payments
Linking /cloudclusters/erpnext/frappe-bench/apps/frappe_whatsapp/frappe_whatsapp/public to ./assets/frappe_whatsapp
:heavy_check_mark: Application Assets Linked

yarn run v1.22.19
$ node esbuild --production --run-build-command

Error: The service was stopped
at /cloudclusters/erpnext/frappe-bench/apps/frappe/node_modules/esbuild/lib/main.js:1356:25
at /cloudclusters/erpnext/frappe-bench/apps/frappe/node_modules/esbuild/lib/main.js:678:9
at Socket.afterClose (/cloudclusters/erpnext/frappe-bench/apps/frappe/node_modules/esbuild/lib/main.js:656:7)
at Socket.emit (node:events:526:35)
at endReadableNT (node:internal/streams/readable:1359:12)
at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
info Visit yarn run | Yarn for documentation about this command.
ERROR There were some problems during build
Terminated
error Command failed with exit code 143.
Traceback (most recent call last):
File “/usr/lib/python3.10/runpy.py”, line 196, in _run_module_as_main
return _run_code(code, main_globals, None,
File “/usr/lib/python3.10/runpy.py”, line 86, in _run_code
exec(code, run_globals)
File “/cloudclusters/erpnext/frappe-bench/apps/frappe/frappe/utils/bench_helper.py”, line 114, in
main()
File “/cloudclusters/erpnext/frappe-bench/apps/frappe/frappe/utils/bench_helper.py”, line 20, in main
click.Group(commands=commands)(prog_name=“bench”)
File “/cloudclusters/erpnext/frappe-bench/env/lib/python3.10/site-packages/click/core.py”, line 1157, in call
return self.main(*args, **kwargs)
File “/cloudclusters/erpnext/frappe-bench/env/lib/python3.10/site-packages/click/core.py”, line 1078, in main
rv = self.invoke(ctx)
File “/cloudclusters/erpnext/frappe-bench/env/lib/python3.10/site-packages/click/core.py”, line 1688, in invoke
return _process_result(sub_ctx.command.invoke(sub_ctx))
File “/cloudclusters/erpnext/frappe-bench/env/lib/python3.10/site-packages/click/core.py”, line 1688, in invoke
return _process_result(sub_ctx.command.invoke(sub_ctx))
File “/cloudclusters/erpnext/frappe-bench/env/lib/python3.10/site-packages/click/core.py”, line 1434, in invoke
return ctx.invoke(self.callback, **ctx.params)
File “/cloudclusters/erpnext/frappe-bench/env/lib/python3.10/site-packages/click/core.py”, line 783, in invoke
return _callback(*args, **kwargs)
File “/cloudclusters/erpnext/frappe-bench/apps/frappe/frappe/commands/utils.py”, line 77, in build
bundle(
File “/cloudclusters/erpnext/frappe-bench/apps/frappe/frappe/build.py”, line 257, in bundle
frappe.commands.popen(command, cwd=frappe_app_path, env=get_node_env(), raise_err=True)
File “/cloudclusters/erpnext/frappe-bench/apps/frappe/frappe/commands/init.py”, line 97, in popen
raise subprocess.CalledProcessError(return
, command)
subprocess.CalledProcessError: Command ‘yarn run production --run-build-command && cd billing && yarn build’ returned non-zero exit status 143.

Hi,

It may help to say the operating environment and version of Frappe and any apps, and whether in development or production.

The error may be related to resource constraints. The amount of RAM may be a factor.