Rapid increase in RAM consumption on the server after normal operation about meshcentral HOT 5 CLOSED

This is a dupe.
Please search before posting new issue

from meshcentral.

This is a dupe. Please search before posting new issue

I have searched many times in the search, I have not found anything. Maybe I didn't search well.

from meshcentral.

Data from journalctl:

node[722]: ERR: /root/meshcentral/node_modules/meshcentral/meshuser.js:792
node[722]: if ((docs[i].rdp != null) && (docs[i].rdp[obj.user._id] != null)) { docs[i].rdp = 1; } else { delete docs[i].rdp; }
node[722]: ^
node[722]: TypeError: Cannot read properties of undefined (reading '_id')
node[722]: at /root/meshcentral/node_modules/meshcentral/meshuser.js:792:80
node[722]: at /root/meshcentral/node_modules/meshcentral/db.js:2571:54
node[722]: at /root/meshcentral/node_modules/mongodb/lib/utils.js:349:28
node[722]: at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
node[722]: Node.js v18.20.2
node[722]: Error: Command failed: /usr/bin/node /root/meshcentral/node_modules/meshcentral --launch 722
node[722]: (node:2384) Warning: An error event has already been emitted on the socket. Please use the destroy method on the socket while handling a 'clientError' event.
node[722]: (Use node --trace-warnings ... to show where the warning was created)
node[722]: /root/meshcentral/node_modules/meshcentral/meshuser.js:792
node[722]: if ((docs[i].rdp != null) && (docs[i].rdp[obj.user._id] != null)) { docs[i].rdp = 1; } else { delete docs[i].rdp; }
node[722]: ^
node[722]: TypeError: Cannot read properties of undefined (reading '_id')
node[722]: at /root/meshcentral/node_modules/meshcentral/meshuser.js:792:80
node[722]: at /root/meshcentral/node_modules/meshcentral/db.js:2571:54
node[722]: at /root/meshcentral/node_modules/mongodb/lib/utils.js:349:28
node[722]: at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
node[722]: Node.js v18.20.2
node[722]: at ChildProcess.exithandler (node:child_process:422:12)
node[722]: at ChildProcess.emit (node:events:529:35)
node[722]: at maybeClose (node:internal/child_process:1098:16)
node[722]: at ChildProcess._handle.onexit (node:internal/child_process:303:5) {
node[722]: code: 1,
node[722]: killed: false,
node[722]: signal: null,
node[722]: cmd: '/usr/bin/node /root/meshcentral/node_modules/meshcentral --launch 722'
node[722]: }
node[722]: ERROR: MeshCentral failed with critical error, check mesherrors.txt. Restarting in 5 seconds...
node[722]: MeshCentral HTTP redirection server running on port 80.
node[722]: MeshCentral v1.1.23, WAN mode, Production mode.
node[722]: MeshCentral Intel(R) AMT server running on DOMAIN:4433.
node[722]: MeshCentral HTTPS server running on DOMAIN:443.

from meshcentral.

@sheshko-as plz open a separate issue for ur bug above, it is unrelated to the ram increase bug

from meshcentral.

ok

from meshcentral.