Open devisn opened 6 years ago
_logs
For more information, see the CONTRIBUTING guide.
CONTRIBUTING
Run across "JavaScript heap out of memory" error after a 60+ hours uptime.
Expected behavior: [What you expected to happen]
There should be no fatal error cases
Actual behavior: [What actually happened]
0.5.5/e9d4379
You can get this information:
docker run --name bcnode -p 3000:3000 blockcollider/bcnode:0.5.5 start --ws --rovers --ui --node --miner-key aspire > bcnode.log 2> bcnode.err
Attach the complete console output of the docker session (obtained by "> bcnode.log 2> bcnode.err")
bcnode-err.zip bcnode-log.z01.zip bcnode-log.zip
Prerequisites
_logs
directory)For more information, see the
CONTRIBUTING
guide.Description
Run across "JavaScript heap out of memory" error after a 60+ hours uptime.
Steps to Reproduce
Expected behavior: [What you expected to happen]
There should be no fatal error cases
Actual behavior: [What actually happened]
The node produces the fatal error message in console logs (2> .err output file):
FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory 1: node::Abort() [node] 2: 0x11e7fec [node] 3: v8::Utils::ReportOOMFailure(char const, bool) [node] 4: v8::internal::V8::FatalProcessOutOfMemory(char const, bool) [node] 5: v8::internal::Factory::NewUninitializedFixedArray(int) [node] 6: 0xdee3b3 [node] 7: v8::internal::Runtime_GrowArrayElements(int, v8::internal::Object*, v8::internal::Isolate) [node] 8: 0x3b81445842fd
Versions
0.5.5/e9d4379
Application (required)
You can get this information:
docker run --name bcnode -p 3000:3000 blockcollider/bcnode:0.5.5 start --ws --rovers --ui --node --miner-key aspire > bcnode.log 2> bcnode.err
Environment (optional but helpful)
Logs
Attach the complete console output of the docker session (obtained by "> bcnode.log 2> bcnode.err")
bcnode-err.zip bcnode-log.z01.zip bcnode-log.zip