Dokploy OOM issue on Requests tab

[henriklovhaug]

To Reproduce

1. Open requests tab
2. Crash

This is not replicate-able on all systems. I have two VPS with Dokploy running, and they are not linked in any way. This issue only happens on one of them. The system it happens on also have more resources available, but is running more services than the other.

Logs:

user@my-vps:~$ docker logs 80b9ab5c67c5 -f

> [email protected] start /app
> node -r dotenv/config dist/server.mjs

Default middlewares already exists
Network is already initilized
Main config already exists
Default traefik config already exists
Postgres Started ✅
Traefik Started ✅
Redis Started ✅
Setting up cron jobs....
{
  severity_local: 'NOTICE',
  severity: 'NOTICE',
  code: '42P06',
  message: 'schema "drizzle" already exists, skipping',
  file: 'schemacmds.c',
  line: '132',
  routine: 'CreateSchemaCommand'
}
{
  severity_local: 'NOTICE',
  severity: 'NOTICE',
  code: '42P07',
  message: 'relation "__drizzle_migrations" already exists, skipping',
  file: 'parse_utilcmd.c',
  line: '207',
  routine: 'transformCreateStmt'
}
Migration complete
Server Started: 3000
Starting Deployment Worker
FATAL ERROR: v8::ToLocalChecked Empty MaybeLocal
 1: 0xc99970 node::Abort() [node]
 2: 0xb6feda node::OOMErrorHandler(char const*, v8::OOMDetails const&) [node]
 3: 0xebfb60 v8::api_internal::ToLocalEmpty() [node]
 4: 0xca0d9c  [node]
 5: 0x77090284d546
Aborted (core dumped)
 ELIFECYCLE  Command failed with exit code 134.

Current vs. Expected behavior

I click on the the requests tab and Dokploy crashes

Provide environment information

OS: Ubuntu
VPS: Azure VM
CPU: 4 vCPU
RAM: 16 GB
RAM available at crash: 7.36 GiB
Disk available at crash: ~80 GB

Which area(s) are affected? (Select all that apply)

Application

Are you deploying the applications where Dokploy is installed or on a remote server?

Same server where Dokploy is installed

Additional context

Discord discussion thread

Drugde believes, and I concur, that when I open the requests tab, I hit Node.js' 1.4GB RAM limit.

Will you send a PR to fix it?

No