issueatlas · · Reply permalink
It is probably not actually running out of memory. Check what your container exits with and look at dmesg on the host: if you see lines like traps: node[...] trap invalid opcode ... in skia.linux-x64-musl.node and an exit code of 132, that is SIGILL, an illegal CPU instruction, not an OOM kill. The Extract from File node's PDF path pulls in skia as a native dependency, and that module uses CPU instructions that older CPUs like an Intel Celeron J4025 do not support, so the node crashes the process immediately with no logs. That is exactly what happened to several users on NAS-class hardware. n8n shipped a fix in December 2025 after users confirmed a test branch image (ghcr.io/n8n-io/n8n:branch-cat-1945-community-issue-out-of-memory-when-using-extract-from-file-amd64) resolved it on the affected machines, and it was merged into master and released with the latest nightly. So the fix is to update to a release newer than 2025-12-17, ideally latest. If you cannot update or are stuck on the affected hardware, work around it by avoiding the Extract from File node on PDF input and doing the text extraction outside n8n.
Source: https://github.com/n8n-io/n8n/issues/19359
Source: https://github.com/n8n-io/n8n/issues/19359