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
FATAL ERROR: v8::ToLocalChecked Empty MaybeLocal ----- Native stack trace ----- 1: 0xde0c10 node::Abort() [node] 2: 0xcb1f63 node::OOMErrorHandler(char const*, v8::OOMDetails const&) [node] 3: 0x102a180 v8::api_internal::ToLocalEmpty() [node] 4: 0xde801c [node] 5: 0x7fdf9ddceadd ----- JavaScript stack trace ----- 1: readFileSync (node:fs:453:20) 2: vs (/home/justin/Git/link-inspector/dist/index.js:2:1052) 3: /home/justin/Git/link-inspector/dist/index.js:13:504 4: Ir (/home/justin/Git/link-inspector/dist/index.js:13:458) 5: u (/home/justin/Git/link-inspector/dist/index.js:13:681) 6: /home/justin/Git/link-inspector/dist/index.js:13:708 7: processTicksAndRejections (node:internal/process/task_queues:95:5) Aborted (core dumped)
This error happens when running https://github.com/ubccsss/ubccsss.org on a Intel i5-8365U with 16G of ram. This is a out of RAM error. The solution is to use pipes.
Documentation: https://nodejs.org/docs/v0.5.10/api/streams.html#stream.pipe Stack over flow on the issue: https://stackoverflow.com/questions/7883698/node-js-is-running-out-of-memory-on-large-bit-by-bit-file-read
The text was updated successfully, but these errors were encountered:
Fixed in #47
Sorry, something went wrong.
No branches or pull requests
This error happens when running https://github.com/ubccsss/ubccsss.org on a Intel i5-8365U with 16G of ram. This is a out of RAM error. The solution is to use pipes.
Documentation: https://nodejs.org/docs/v0.5.10/api/streams.html#stream.pipe
Stack over flow on the issue: https://stackoverflow.com/questions/7883698/node-js-is-running-out-of-memory-on-large-bit-by-bit-file-read
The text was updated successfully, but these errors were encountered: