Processing images (xxx images) - 0% Processing images (xxx images) - 4% Killed

Hello!
I’m with a free account and I neved had this issue but the process is Killed while processing the images.
Is it due to limitations?
Thanks

5:46:59 PM: Compile assets - 61.25s
5:47:00 PM: Execute GraphQL (54 queries) - 0.4s
5:47:02 PM: Render HTML (54 files) - 2.14s
5:47:02 PM: Process files (4 files) - 0.32s
5:47:31 PM: Processing images (643 images) - 0%Processing images (643 images) - 4%Killed
5:47:32 PM: npm ERR! code ELIFECYCLE
5:47:32 PM: npm ERR! errno 137
5:47:32 PM: npm ERR! gridsome-starter-shopify@ build: gridsome build
5:47:32 PM: npm ERR! Exit status 137
5:47:32 PM: npm ERR!
5:47:32 PM: npm ERR! Failed at the gridsome-starter-shopify@ build script.
5:47:32 PM: npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
5:47:32 PM: npm ERR! A complete log of this run can be found in:
5:47:32 PM: npm ERR! /opt/buildhome/.npm/_logs/2022-09-02T15_47_32_237Z-debug.log
5:47:33 PM: ​
5:47:33 PM: ────────────────────────────────────────────────────────────────
5:47:33 PM: “build.command” failed
5:47:33 PM: ────────────────────────────────────────────────────────────────
5:47:33 PM: ​
5:47:33 PM: Error message
5:47:33 PM: Command failed with exit code 137: npm run build (Search results for '"non-zero exit code: 137"' - Netlify Support Forums)
5:47:33 PM: ​
5:47:33 PM: Error location
5:47:33 PM: In Build command from Netlify app:
5:47:33 PM: npm run build

Resolved config
9:50:54 AM: build:
9:50:54 AM: command: npm run build
9:50:54 AM: commandOrigin: ui
9:50:54 AM: environment:
9:50:54 AM: - GRIDSOME_SHOPIFY_STOREFRONT
9:50:54 AM: - GRIDSOME_SHOPIFY_STOREFRONT_TOKEN
9:50:54 AM: publish: /opt/build/repo/dist
9:50:54 AM: publishOrigin: ui
9:50:55 AM: events.js:377
9:50:55 AM: throw er; // Unhandled ‘error’ event
9:50:55 AM: ^
9:50:55 AM: Error [ERR_IPC_CHANNEL_CLOSED]: Channel closed
9:50:55 AM: at new NodeError (internal/errors.js:322:7)
9:50:55 AM: at process.target.send (internal/child_process.js:736:16)
9:50:55 AM: at reportSuccess (/opt/build/repo/node_modules/jest-worker/build/workers/processChild.js:91:11)
9:50:55 AM: Emitted ‘error’ event on process instance at:
9:50:55 AM: at internal/child_process.js:740:35
9:50:55 AM: at processTicksAndRejections (internal/process/task_queues.js:77:11) {
9:50:55 AM: code: ‘ERR_IPC_CHANNEL_CLOSED’
9:50:55 AM: }
9:50:55 AM: events.js:377
9:50:55 AM: throw er; // Unhandled ‘error’ event
9:50:55 AM: ^
9:50:55 AM: Error [ERR_IPC_CHANNEL_CLOSED]: Channel closed
9:50:55 AM: at new NodeError (internal/errors.js:322:7)
9:50:55 AM: at process.target.send (internal/child_process.js:736:16)
9:50:55 AM: at reportSuccess (/opt/build/repo/node_modules/jest-worker/build/workers/processChild.js:91:11)
9:50:55 AM: Emitted ‘error’ event on process instance at:
9:50:55 AM: at internal/child_process.js:740:35
9:50:55 AM: at processTicksAndRejections (internal/process/task_queues.js:77:11) {
9:50:55 AM: code: ‘ERR_IPC_CHANNEL_CLOSED’
9:50:55 AM: }
9:50:56 AM: Caching artifacts
9:50:56 AM: Started saving node modules
9:50:56 AM: events.js:377
9:50:56 AM: throw er; // Unhandled ‘error’ event
9:50:56 AM: ^
9:50:56 AM: Error [ERR_IPC_CHANNEL_CLOSED]: Channel closed
9:50:56 AM: at new NodeError (internal/errors.js:322:7)
9:50:56 AM: at process.target.send (internal/child_process.js:736:16)
9:50:56 AM: at reportSuccess (/opt/build/repo/node_modules/jest-worker/build/workers/processChild.js:91:11)
9:50:56 AM: Emitted ‘error’ event on process instance at:
9:50:56 AM: at internal/child_process.js:740:35
9:50:56 AM: at processTicksAndRejections (internal/process/task_queues.js:77:11) {
9:50:56 AM: code: ‘ERR_IPC_CHANNEL_CLOSED’
9:50:56 AM: }
9:50:56 AM: Finished saving node modules
9:50:56 AM: Started saving build plugins
9:50:57 AM: Finished saving build plugins
9:50:57 AM: Started saving yarn cache
9:50:57 AM: events.js:377
9:50:57 AM: throw er; // Unhandled ‘error’ event
9:50:57 AM: ^
9:50:57 AM: Error [ERR_IPC_CHANNEL_CLOSED]: Channel closed
9:50:57 AM: at new NodeError (internal/errors.js:322:7)
9:50:57 AM: at process.target.send (internal/child_process.js:736:16)
9:50:57 AM: at reportError (/opt/build/repo/node_modules/jest-worker/build/workers/processChild.js:111:11)
9:50:57 AM: at reportClientError (/opt/build/repo/node_modules/jest-worker/build/workers/processChild.js:95:10)
9:50:57 AM: at processTicksAndRejections (internal/process/task_queues.js:95:5)
9:50:57 AM: Emitted ‘error’ event on process instance at:
9:50:57 AM: at processEmit [as emit] (/opt/build/repo/node_modules/signal-exit/index.js:199:34)
9:50:57 AM: at internal/child_process.js:740:35
9:50:57 AM: at processTicksAndRejections (internal/process/task_queues.js:77:11) {
9:50:57 AM: code: ‘ERR_IPC_CHANNEL_CLOSED’
9:50:57 AM: }
9:50:57 AM: events.js:377
9:50:57 AM: throw er; // Unhandled ‘error’ event
9:50:57 AM: ^
9:50:57 AM: Error [ERR_IPC_CHANNEL_CLOSED]: Channel closed
9:50:57 AM: at new NodeError (internal/errors.js:322:7)
9:50:57 AM: at process.target.send (internal/child_process.js:736:16)
9:50:57 AM: at reportError (/opt/build/repo/node_modules/jest-worker/build/workers/processChild.js:111:11)
9:50:57 AM: at reportClientError (/opt/build/repo/node_modules/jest-worker/build/workers/processChild.js:95:10)
9:50:57 AM: at processTicksAndRejections (internal/process/task_queues.js:95:5)
9:50:57 AM: Emitted ‘error’ event on process instance at:
9:50:57 AM: at processEmit [as emit] (/opt/build/repo/node_modules/signal-exit/index.js:199:34)
9:50:57 AM: at internal/child_process.js:740:35
9:50:57 AM: at processTicksAndRejections (internal/process/task_queues.js:77:11) {
9:50:57 AM: code: ‘ERR_IPC_CHANNEL_CLOSED’
9:50:57 AM: }
9:50:57 AM: events.js:377
9:50:57 AM: throw er; // Unhandled ‘error’ event
9:50:57 AM: ^

I switched to Vercel and it works.