We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Before submitting a bug please read: https://zwave-js.github.io/zwavejs2mqtt/#/troubleshooting/bug_report
Build/Run method
out of memory error.
Logs from my docker stdout:
�[90m2021-02-08 11:15:35.101�[39m �[32mINFO�[39m �[1mZWAVE�[22m: Node 8: value updated: 112-0-82 6500 => 6500 �[90m2021-02-08 11:15:35.510�[39m �[32mINFO�[39m �[1mZWAVE�[22m: Node 8: interview completed, all values are updated FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory <--- Last few GCs ---> [1:0x55a3a19ddee0] 1546374 ms: Scavenge 2041.4 (2047.5) -> 2039.6 (2047.5) MB, 6.2 / 0.0 ms (average mu = 0.231, current mu = 0.131) allocation failure [1:0x55a3a19ddee0] 1546407 ms: Scavenge 2041.5 (2047.5) -> 2039.6 (2047.5) MB, 6.8 / 0.0 ms (average mu = 0.231, current mu = 0.131) allocation failure [1:0x55a3a19ddee0] 1546437 ms: Scavenge 2041.5 (2047.5) -> 2039.7 (2051.5) MB, 5.9 / 0.0 ms (average mu = 0.231, current mu = 0.131) allocation failure
<--- JS stacktrace --->
store.zip
The text was updated successfully, but these errors were encountered:
@cazador481 Copuld you provide some more info about the error? the stack trace seems incomplete
Sorry, something went wrong.
Alas that is all I have, I'll close this and if I get another crash with more info I'll make a new report.
robertsLando
No branches or pull requests
Before submitting a bug please read: https://zwave-js.github.io/zwavejs2mqtt/#/troubleshooting/bug_report
Version
Build/Run method
Describe the bug
out of memory error.
Logs from my docker stdout:
<--- JS stacktrace --->
store.zip
The text was updated successfully, but these errors were encountered: