Persistent issues with yarn exiting with exit code 137

Issues
1

I have persistent issues with yarn exiting when running the self hosted version.

When run with yarn --verbose dev:

...
$ next dev
ready - started server on 0.0.0.0:3000, url: <http://localhost:3000>
event - compiled client and server successfully in 2.6s (171 modules)
wait  - compiling /plasmic-host (client and server)...
event - compiled client and server successfully in 24.9s (2327 modules)
Plasmic: Setting up app host dependencies
USING cache /workspaces/ProbityManager/.next/.plasmic/plasmic-piMK6NLBTa6BVDMyEBbMme@-preview-cache.json
Subscribing to Plasmic changes...
Killed
verbose 131.504534 Error: Command failed with exit code 137.
    at ProcessTermError.ExtendableBuiltin (/usr/share/yarn/lib/cli.js:721:66)
    at ProcessTermError.MessageError (/usr/share/yarn/lib/cli.js:750:123)
    at new ProcessTermError (/usr/share/yarn/lib/cli.js:790:113)
    at /usr/share/yarn/lib/cli.js:34672:30
    at Generator.throw (<anonymous>)
    at step (/usr/share/yarn/lib/cli.js:310:30)
    at /usr/share/yarn/lib/cli.js:323:13
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
error Command failed with exit code 137.

Have played around for 30 mins trying to get it to work without luck. I am doing all of this inside a vscode devcontainer, but that shouldn’t make a difference.