Neuer ioBroker-Blog online: Monatsrückblick März/April 2026

[UweRLP]

Hallo.

Hatte im Log mal wieder eine Fehlermeldung die ich nicht richtig interpretieren kann.

host.HP-ED800(ioBroker210b)	2019-12-30 12:07:39.937	error	instance system.adapter.admin.0 terminated with code 134 (134)
host.HP-ED800(ioBroker210b)	2019-12-30 12:07:39.937	error	Caught by controller[4]: 13: 000003D822E5C5C1
host.HP-ED800(ioBroker210b)	2019-12-30 12:07:39.937	error	Caught by controller[4]: 12: 00007FF7D3877676 v8::internal::operator<<+73494
host.HP-ED800(ioBroker210b)	2019-12-30 12:07:39.937	error	Caught by controller[4]: 11: 00007FF7D37FA487 v8::internal::Factory::NewFillerObject+55
host.HP-ED800(ioBroker210b)	2019-12-30 12:07:39.937	error	Caught by controller[4]: 10: 00007FF7D36D01E6 v8::internal::Heap::MaxHeapGrowingFactor+2454
host.HP-ED800(ioBroker210b)	2019-12-30 12:07:39.937	error	Caught by controller[4]: 9: 00007FF7D36D0167 v8::internal::Heap::MaxHeapGrowingFactor+2327
host.HP-ED800(ioBroker210b)	2019-12-30 12:07:39.937	error	Caught by controller[4]: 8: 00007FF7D36C741C v8::internal::ScavengeJob::operator=+17980
host.HP-ED800(ioBroker210b)	2019-12-30 12:07:39.937	error	Caught by controller[4]: 7: 00007FF7D36C8DC6 v8::internal::ScavengeJob::operator=+24550
host.HP-ED800(ioBroker210b)	2019-12-30 12:07:39.937	error	Caught by controller[4]: 6: 00007FF7D36D1DE4 v8::internal::Heap::MaxHeapGrowingFactor+9620
host.HP-ED800(ioBroker210b)	2019-12-30 12:07:39.937	error	Caught by controller[4]: 5: 00007FF7D34EB5EF v8::internal::FatalProcessOutOfMemory+639
host.HP-ED800(ioBroker210b)	2019-12-30 12:07:39.937	error	Caught by controller[4]: al::FatalProcessOutOfMemory+846
host.HP-ED800(ioBroker210b)	2019-12-30 12:07:39.937	error	Caught by controller[3]: 4: 00007FF7D34EB6BE v8::intern
host.HP-ED800(ioBroker210b)	2019-12-30 12:07:39.937	error	Caught by controller[3]: 3: 00007FF7D31D31F0 node_module_register+2032
host.HP-ED800(ioBroker210b)	2019-12-30 12:07:39.937	error	Caught by controller[3]: 2: 00007FF7D31D2876 node::MakeCallback+4534
host.HP-ED800(ioBroker210b)	2019-12-30 12:07:39.937	error	Caught by controller[3]: ::internal::GCIdleTimeHandler::GCIdleTimeHandler+4506
host.HP-ED800(ioBroker210b)	2019-12-30 12:07:39.937	error	Caught by controller[2]: 1: 00007FF7D31F7DDA v8
host.HP-ED800(ioBroker210b)	2019-12-30 12:07:39.937	error	Caught by controller[1]: ark-compacts near heap limit Allocation failed - JavaScript heap out of memory
system.adapter.admin.0: logging false
host.HP-ED800(ioBroker210b)	2019-12-30 12:07:39.936	error	Caught by controller[0]: FATAL ERROR: Ineffective m

Soweit ich es verstehe geht dem Admin Adapter wohl der Speicher aus.
Welcher Spreicher ist damit gemeint? RAM auf dem Server oder auf dem Client (Browser) oder Plattenplatz (Cache?).
Kann ich da was ändern bzw. optimieren?
Admin Adapter ist die Version 3.7.5

Systemdata	Bitte Ausfüllen
Hardwaresystem:	HP EliteDesk 800 G1 USDT QuadCore Core i5-4570S
Arbeitsspeicher:	8 GB
Festplattenart:	SSD 128GB
Betriebssystem:	Windows 10 pro x64
Node-Version:	10.x.x
Nodejs-Version:	v10.17.0
NPM-Version:	6.11.3
Installationsart:	Installer