New error

File uploaded. filePath: backups/2cdd62c5-41af-48a4-94fc-bcb897495977/files/faf84d8b-866d-30a5-970f-13c51a3d7da6.png; fileId: 9afbb5b0-7a7c-48a2-8381-58465447596b
 -------------------------- pas-explorer, sandbox_support.is --------------------------
 --- dropAllCollections start
 --- dropAllCollections end
 --- restoreCollectionFromFileUsingStream start
 --- restoreCollectionFromFileUsingStream end
 --- updateMany
 --- restoreCollectionFromFileUsingStream start
 --- restoreCollectionFromFileUsingStream end
 -------------------------- pas-models, sandbox_support.is --------------------------
 --- dropAllCollections start
 --- dropAllCollections end
 --- restoreCollectionFromFileUsingStream start

<--- Last few GCs --->

[142036:0x55bdc784ff00]  1374201 ms: Mark-sweep 2040.8 (2055.2) -> 2038.1 (2055.2) MB, 1132.2 / 0.0 ms  (average mu = 0.253, current mu = 0.122) allocation failure scavenge might not succeed
[142036:0x55bdc784ff00]  1375404 ms: Mark-sweep 2041.1 (2055.2) -> 2038.9 (2056.2) MB, 1148.9 / 0.0 ms  (average mu = 0.166, current mu = 0.046) allocation failure scavenge might not succeed


<--- JS stacktrace --->

==== JS stack trace =========================================

    0: ExitFrame [pc: 0x7f8ebbd8ab79]
Security context: 0x259751f5b9a1 <JSObject>
    1: /* anonymous */ [0x28ad54511a19] [/home/svidenovic/TIAC/scheer_modeler/model-editor-service/node_modules/jsonparse/jsonparse.js:~342] [pc=0x603ddfd56da](this=0x19fc2873f5a1 <Parser map = 0x3ed5a58acf89>,1,0x259751f68d51 <String[#1]: {>)
    2: /* anonymous */ [0xad295093f21] [/home/svidenovic/TIAC/scheer_modeler/model-editor-service/node_modules/JSONS...

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
 1: 0x7f8ebaec83cc node::Abort() [/lib/x86_64-linux-gnu/libnode.so.72]
 2: 0x7f8ebadf867c  [/lib/x86_64-linux-gnu/libnode.so.72]
 3: 0x7f8ebb29de2a v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [/lib/x86_64-linux-gnu/libnode.so.72]
 4: 0x7f8ebb29e1e4 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [/lib/x86_64-linux-gnu/libnode.so.72]
 5: 0x7f8ebb450509  [/lib/x86_64-linux-gnu/libnode.so.72]
 6: 0x7f8ebb460dc6 v8::internal::Heap::PerformGarbageCollection(v8::internal::GarbageCollector, v8::GCCallbackFlags) [/lib/x86_64-linux-gnu/libnode.so.72]
 7: 0x7f8ebb461c12 v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [/lib/x86_64-linux-gnu/libnode.so.72]
 8: 0x7f8ebb463fbd v8::internal::Heap::AllocateRawWithLightRetry(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [/lib/x86_64-linux-gnu/libnode.so.72]
 9: 0x7f8ebb464029 v8::internal::Heap::AllocateRawWithRetryOrFail(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [/lib/x86_64-linux-gnu/libnode.so.72]
10: 0x7f8ebb428d43 v8::internal::Factory::NewFillerObject(int, bool, v8::internal::AllocationType, v8::internal::AllocationOrigin) [/lib/x86_64-linux-gnu/libnode.so.72]
11: 0x7f8ebb77e6e7 v8::internal::Runtime_AllocateInYoungGeneration(int, unsigned long*, v8::internal::Isolate*) [/lib/x86_64-linux-gnu/libnode.so.72]
12: 0x7f8ebbd8ab79  [/lib/x86_64-linux-gnu/libnode.so.72]
Aborted (core dumped)
npm ERR! code ELIFECYCLE
npm ERR! errno 134
npm ERR! model-editor-service@2.2.0 start: `node dist/source/service.js`
npm ERR! Exit status 134
npm ERR!
npm ERR! Failed at the model-editor-service@2.2.0 start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/svidenovic/.npm/_logs/2023-03-20T09_15_00_218Z-debug.log
npm ERR! code ELIFECYCLE
npm ERR! errno 134
npm ERR! model-editor-service@2.2.0 compile-start: `npm run compile && npm run start`
npm ERR! Exit status 134
npm ERR!
npm ERR! Failed at the model-editor-service@2.2.0 compile-start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/svidenovic/.npm/_logs/2023-03-20T09_15_00_250Z-debug.log